Optical fluid sensors for cross contamination control systems

ABSTRACT

An optical fluid sensor (OFS) is disclosed that includes a body defining a chamber and having one or more apertures to allow a fluid to enter the chamber, a light source optically coupled to the chamber and configured to emit light into the chamber, and a detector optically coupled to the chamber and configured to receive light from the chamber. The light source may emit IR, visible, and UV light into the chamber, and the detector may measure an intensity of one or more wavelengths of IR or visible light received by the detector. When fluid is disposed within the chamber, the light emitted by the light source may pass into and through the fluid disposed in the chamber before being received by the detector. A crossover protection system is also disclosed that includes an OFS for determining a transported liquid type.

FIELD

Embodiments of the present disclosure are related to optical fluidsensors, in particular optical fluid sensors for identifying fluids.

BACKGROUND

Transporting liquids, whether by tanker truck, railcar, through transferconduits, or through other methods, involves transferring the liquidproduct from one vessel or tank to another vessel or tank.Conventionally, the process of transferring liquid products betweenvessels and/or tanks relies on an operator to ensure that two differentliquids are not mixed in the tanks. Mistakenly mixing differing liquidproducts, such as different fuel products, can be a costly mistake.Conventional liquid property sensors utilized to help identify liquidproducts and avoid inadvertently mixing different liquid products arenot be capable of distinguishing between certain types of liquids.

SUMMARY

Accordingly, an ongoing need exists for improved liquid property sensorsfor identifying the type of liquid product or fluid being transferredbetween storage vessels or tanks. Embodiments of the present disclosureare directed to optical fluid sensors and crossover protection systemsutilizing the optical fluid sensors.

According to one or more embodiments, an optical fluid sensor maycomprise a body defining a chamber and having one or more apertures toallow a fluid to enter the chamber, a light source optically coupled tothe chamber and configured to emit light into the chamber, and adetector optically coupled to the chamber and configured to receivelight from the chamber. The detector may measure an intensity of one ormore wavelengths of light received by the detector. The light source andthe detector may be positioned such that, when fluid is disposed withinthe chamber, emitted light from the light source passes into and throughthe fluid disposed in the chamber before being received by the detector.

According to one or more other embodiments, a fuel sensor may comprise alight source optically coupleable to an enclosed volume and configuredto emit IR, visible, and UV spectra light and a detector opticallycoupleable to the enclosed volume and configured to output a signalproportional to an intensity of one or more wavelengths of IR or visiblelight received by the detector. The fuel sensor may further comprise aprocessor, one or more memory modules communicatively coupled to theprocessor, and machine readable instructions stored in the one or morememory modules that cause the fuel sensor to perform at least thefollowing when executed by the processor: send a control signal to thelight source to cause the light source to emit visible light into theenclosed space and emit UV light into the enclosed space, receivevisible light at the detector, process the received light to determinewavelength and intensity information for the received light, anddetermine a fluid type of the fluid in the chamber from the wavelengthand intensity information for the received light.

According to one or more embodiments, an optical sensor system maycomprise a light source configured to emit UV light into a fluid, and adetector configured to measure intensities of one or more wavelengths ofvisible light fluoresced by the fluid in response to the UV lightemitted by the light source. The optical sensor system may furthercomprise a processor, one or more memory modules communicatively coupledto the processor, and machine readable instructions stored in the one ormore memory modules that cause the optical sensor system to perform atleast the following when executed by the processor: transmit a controlsignal to the light source to cause the light source to emit the UVlight into the fluid to cause the fluid to fluoresce, receive visiblelight at the detector, process the received light to determinewavelength and intensity information for the received light, compare thewavelength and intensity information for the received light to one ormore fluid profiles stored in the one or more memory modules, whereineach of the one or more fluid profiles comprises information on one ormore fluorescent properties of the fluid, and determine a fluid type ofthe fluid based on the comparison.

According to one or more other embodiments, a crossover protectionsystem may comprise a product transport vehicle comprising a tankcompartment for containing a liquid product and a valve coupled to thetank compartment, the valve regulating a flow of liquid product from thetank compartment and having a normally locked state. The crossoverprotection system may further comprise an optical fluid sensorpositioned to contact the liquid product stored in the tank compartment.The optical fluid sensor may comprise a body defining a chamber andhaving one or more apertures to allow the liquid product to enter thechamber, a light source optically coupled to the chamber and configuredto emit light into the chamber, and a detector optically coupled to thechamber and configured to receive light from the chamber. The detectormay measure an intensity of one or more wavelengths of light received bythe detector. The light source and the detector may be positioned suchthat, when fluid is disposed within the chamber, light passes into andthrough the fluid disposed within the chamber before being received bythe detector. The crossover protection system may further comprise atank delivery connector fluidly coupled to a distribution side of thevalve. The tank delivery connector may comprise a tank tag reader forinterrogating a tank tag coupled to a distribution tank separate fromthe product transport vehicle to retrieve a stored liquid type encodedon the tank tag. The stored liquid type may be indicative of a fluidtype of the liquid product in the distribution tank. The crossoverprotection system may further comprise a system controllercommunicatively coupled to the valve, the optical fluid sensor, and thetank delivery connector. The system controller may comprise a processorand one or more memory modules.

These and additional features provided by the embodiments describedherein will be more fully understood in view of the following detaileddescription, in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments set forth in the drawings are illustrative and exemplaryin nature and not intended to limit the subject matter defined by theclaims. The following detailed description of the illustrativeembodiments can be understood when read in conjunction with thefollowing drawings, where like structure is indicated with likereference numerals and in which:

FIG. 1 is a front perspective view of an optical fluid sensor, accordingto one or more embodiments shown and described herein;

FIG. 2 is a front cross-sectional view of the optical fluid sensor ofFIG. 1 taken along reference plane 2-2 in FIG. 1, according to one ormore embodiments shown and described herein;

FIG. 3 is an exploded perspective view of the optical fluid sensor ofFIG. 1, according to one or more embodiments shown and described herein;

FIG. 4A schematically depicts an optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 4B schematically depicts an optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 4C schematically depicts an optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 5A schematically depicts an optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 5B schematically depicts an optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 5C schematically depicts an optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 6 schematically depicts an optical sensor system with an opticalfuel sensor, according to one or more embodiments shown and describedherein;

FIG. 7 schematically depicts a flowchart of a method for determiningwhether a fluid is present in the optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 8 schematically depicts a flowchart of a method for determining afluid type of a fluid using the optical fluid sensor, according to oneor more embodiments shown and described herein;

FIG. 9 schematically depicts a product transport vehicle at a productdistribution station according to one or more embodiments shown anddescribed herein;

FIG. 10 schematically depicts a crossover protection control systemaccording to one or more embodiments shown and described herein;

FIG. 11A schematically depicts an electronic product grade indicatorcontroller according to one or more embodiments shown and describedherein;

FIG. 11B schematically depicts a product grade indicator pneumaticsystem according to one or more embodiments shown and described herein;

FIG. 12 schematically depicts the product transport vehicle at a loadingstation according to one or more embodiments shown and described herein;

FIG. 13 schematically depicts the product transport vehicle at thedistribution station according to one or more embodiments shown anddescribed herein;

FIG. 14 is a side view of a tank delivery connector according to one ormore embodiments shown and described herein;

FIG. 15 is a front view of a control valve according to one or moreembodiments shown and described herein;

FIG. 16 is a side view of the control valve according to one or moreembodiments shown and described herein; and

FIG. 17 schematically depicts a fleet management system according to oneor more embodiments shown and described herein.

DETAILED DESCRIPTION

The embodiments disclosed herein include optical fluid sensors (OFS),optical sensor systems that include the OFS disclosed herein, andmethods for determining a fluid type of a fluid or liquid product usingthe OFS and optical sensor systems disclosed herein. Crossoverprotection systems utilizing the OFS and optical sensor systems toprevent co-mingling and crossover contamination of dissimilar liquidproducts during material transfer operations are also disclosed.Referring generally to FIGS. 1 and 2, an OFS of the present disclosuremay include a body that defines a chamber and one or more apertures inthe chamber to allow a fluid, such as a liquid product stored in astorage tank or tank compartment, to enter the chamber. The OFSadditionally may include a light source optically coupled to the chamberand configured to emit light into the chamber. The light source may beconfigured to emit infrared (IR) light, visible light, ultraviolet (UV)light, or combinations of these into the chamber and into the fluiddisposed within the chamber. The OFS may include a detector opticallycoupled to the chamber and configured to receive light from the chamber.The detector may measure wavelengths and intensities of IR and visiblelight received by the detector. The light source and the detector may bepositioned such that, when fluid is disposed within the chamber, thelight emitted by the light source may pass into and through the fluiddisposed in the chamber before being received by the detector. The OFSmay include a processor, one or more memory modules communicativelycoupled to the processor, and machine readable instructions stored inthe memory modules. When executed by the processor, the machine readableinstructions may cause the optical fluid sensor to transmit a controlsignal to the light source to cause the light source to emit IR,visible, or UV light into the chamber, receive IR or visible light atthe detector, process the received light to determine wavelength andintensity information for the received light, compare the wavelength andintensity information for the received light to one or more fluidprofiles stored in the memory modules, and determine a fluid type of thefluid in the chamber based on the comparison of the wavelength andintensity of the received light to the fluid profiles.

The OFS and optical sensor systems disclosed herein may be utilized incrossover protection systems, a non-limiting example of which isgenerally depicted in FIG. 9, to prevent co-mingling of dissimilarliquid products when engaging in material transfer operations. Thecrossover protection system may be mounted on a product transportvehicle, such as a fuel truck, railcar, or other vehicle, for example.The crossover protection system may include a system controller which iscommunicatively coupled to at least one OFS, at least one valve, and atleast one tank tag reader. For each tank compartment on the producttransport vehicle there is an OFS, a valve, and, optionally, anelectronic product grade indicator (PGI) controller to serve as aninterface for the operator and the system controller. The PGI controllermay also assist in controlling the loading and unloading of liquidproduct from the corresponding tank compartment. The system controllercontrols the flow of liquid product to and from each tank compartmentthrough actuation of the valve. If the potential for co-mingling ofdissimilar liquid products in a tank compartment and a distribution tankis present, the system controller prevents the valve corresponding tothe tank compartment from being opened thus preventing the co-minglingand cross contamination of the dissimilar liquid products.

The OFS may be coupled to at least one hose adaptor assembly or tankcompartment such that the OFS may detect a transported fluid type of theliquid product passing through the hose adaptor assembly or contained inthe tank compartment. Accordingly, it should be understood that the OFSmay be positioned to contact a liquid product (fluid) stored in the tankcompartment to determine the fluid type of the liquid product stored inthe tank compartment. The OFS may determine a fluid type. Inembodiments, the transported fluid type, once determined, may be storedin memory and may be indexed according to the correspondingtransportation tank. The OFS may transmit the fluid type in the form ofa transported liquid type or an output signal indicative of the fluidtype to the system controller either directly or through the PGIcontroller.

Referring now to FIGS. 1 and 2, the OFS 130 may include a body 302configured to be inserted into a fuel transfer pipe (e.g., a pipeconnection 50 in FIG. 9), a conduit, a storage tank (e.g., distributiontank 65 in FIG. 1), or a tank compartment 25 (FIG. 9). The body 302 mayinclude a sensor housing 304 disposed at a sensor end 314 of the body302. The sensor end 314 of the body 302 refers to an end of the body 302that is inserted into the transfer pipe, conduit, storage tank, or tankcompartment 25 (FIG. 9) and generally contacts the fluid in the transferpipe, conduit, storage tank, or tank compartment 25. The sensor housing304 may define a chamber 306 and may define one or more apertures 308extending through the sensor housing 304 to enable fluid to flow intothe chamber 306. As used herein, the term “chamber” may refer to a fullyor partially enclosed volume. The apertures 308 may be disposed in anyside of the housing 304 or in an end of the housing 304. In one or moreembodiment, the chamber 308 may be an open-sided recess or pocket in anend of the housing 304 such that the chamber 308 is only partiallyenclosed by the housing 304 and open to the fluid.

Referring to FIG. 2, the OFS 130 may include a light source 310optically coupled to the chamber 306 and configured to emit light intothe chamber 306 and a detector 312 optically coupled to the chamber 306and configured to receive light from the chamber 306. The light source310 may be capable of producing light in the infrared (IR), visible, andultraviolet (UV) spectra. The detector 312 may be capable of measuringthe intensities and wavelengths of IR and visible light received by thedetector 312. The OFS 130 may include an OFS controller 402 (FIG. 6)that receives a signal from the detector 312 indicative of thewavelengths and intensities of light received by the detector 312,processes the signal information from the detector 312 to determine thewavelength and intensity information of the light received at thedetector 312 (i.e., the received light), compares the wavelength andintensity information for the received light to one or more fluidprofiles, and determines a fluid type of the fluid disposed within thechamber 306 based on the comparison of the wavelength and intensityinformation of the received light to the one or more fluid profiles.

Referring to FIGS. 1-3, the body 302 of the OFS 130 may include anelectronics portion 318 coupled to or integral with the sensor housing304. The electronics portion 318 of the body 302 may be generallypositioned at an end of the body opposite the sensor end 314 and may begenerally disposed external to the transfer pipe, conduit, storage tank,or tank compartment to which the OFS 130 is installed. The electronicsportion 318 of the body 302 may not be in contact with the fluid. Aspreviously discussed, the sensor housing 304 defines the chamber 306 andthe one or more apertures 308 that enable fluid to flow into and/or outof the chamber 306. In one or more embodiments, the chamber 306 may bedefined internally within the sensor housing 304 such that the chamber306 is defined by an inner side 320 (FIG. 2) of an outer wall 322 of thesensor housing 304. In one or more embodiments, the sensor housing 304may be cylindrical in shape and the apertures 308 may be disposed in theouter walls 322 of the sensor housing 304. The sensor housing 304 mayhave any other convenient shape.

The body 302 may be configured to couple the OFS 130 to a fitting, suchas the hose adaptor assembly 35 (FIG. 9), for inserting the sensorhousing 304 of the OFS 130 into a fuel transfer pipe, conduit, storagetank, or tank compartment. In one or more embodiments, the body 302 mayinclude a threaded portion 326 for removeably attaching the body 302into the fitting. Although a threaded portion 326 is described herein,it is contemplated that one or more other coupling means, such as clips,welds, or sockets for example, may be utilized for coupling the body 302of the OFS 130 to the fitting. In one or more embodiments, the body 302may be configured to interface and removeably couple with a controlvalve 45 (FIGS. 9 and 16). A non-limiting example of a suitable controlvalve 45 is the API Adaptor, model number 891BA-LK by Civacon. In one ormore embodiments, the body 302 may be removeably coupleable to a port(not shown) positioned in a tank compartment 25 (FIG. 9). The body 302of the OFS 130 may be configured to isolate the detector 312 fromambient sources of light so that the detector 312 is exposed only tolight emitted by the light source 310 into the chamber 306 or visiblelight fluoresced by the fluid in the chamber 306 in response to UV lightemitted by the light source 310.

The body 302 may be constructed of a material compatible with the fluidsand liquid products with which the OFS 130 may come into contact. In oneor more embodiments, the body 302 may be corrosion resistant andchemically resistant. In one or more embodiments, the body 302 may bechemically resistant to organic solvents and/or petroleum-based fuelcompositions.

The light source 310 may be capable of producing IR spectrum light,visible spectrum light, UV spectrum light, or combinations of IR,visible, and UV spectra light. In one or more embodiments, the lightsource 310 may emit IR light, visible light, and UV light. The lightsource 310 may be one or more light emitting diodes (LED). Althoughembodiments comprising LEDs are described subsequently in thisdisclosure, it is contemplated that other types of light emittingdevices may be used in the light source 310 to produce the light.Non-limiting examples of light emitting devices that may be used for thelight source 310 may include, but are not limited to, incandescent lightbulbs, fluorescent lamps, metal-halide lamps, halogen lamps, lasers,neon lamps, argon lamps, or other light emitting devices. LEDs mayinclude, but are not limited to, organic LEDs, polymer LEDs, activematrix organic LEDs, other LEDs, or combinations thereof.

The light source 310 may be a single light emitting device capable ofproducing the different types of light under different operatingconditions, or the light source 310 may include a plurality of lightemitting devices, at least one light emitting device configured to emitat least one of IR light, visible light, or UV light. In one or moreembodiments, the light source 310 may be a single LED and the operatingconditions, such as power input or use of one or more lens filters forexample, may be manipulated to produce IR light, visible light, UVlight, or combinations of these. In one or more embodiments, the lightsource 310 may comprise a plurality of LEDs, at least one of which maybe configured to produce IR light, at least one of which may beconfigured to produce visible light, and at least one of which may beconfigured to produce UV light. In one or more embodiments, the lightsource 310 may include at least one LED producing white light. In one ormore embodiments, the light source 310 may include at least one LEDproducing visible light in the red visible spectrum, at least one LEDproducing visible light in the green visible spectrum, and at least oneLED producing light in the blue visible spectrum. In one or moreembodiments, the light source 310 may comprise multiple LEDs forproducing the visible light, and each of the multiple LEDs may produceone or more of red, orange, yellow, green, blue, or violet spectra ofvisible light. In one or more embodiments, the light source 310 mayinclude six or more LEDs for producing the visible light with at leastone LED for each of the red, orange, yellow, green, blue, and violetwavelength ranges (spectra) of visible light.

The detector 312 may include any device capable of receiving the lightand detecting the wavelength and intensity of light. The detector 312may be capable of detecting the wavelength and intensity of IR light,visible light, or both IR and visible light. The detector 312 may becapable of detecting the wavelength and intensity of other spectra oflight. In one or more embodiments, the detector 312 may be capable ofdetecting the wavelength and intensity of both IR light and visiblelight received by the detector 312. The detector 312 may be configuredto measure the intensity of wavelengths of light received by thedetector 312. The detector 312 may be one or more photo diodes, imagingsystems, or combinations of these. Although embodiments that includephoto diodes are described in further detail in this disclosure, it iscontemplated that other types of detectors or detection systems capableof measuring wavelengths and intensities of IR or visible light may beused in the OFS 130. In one or more embodiments, the detector 312 may beadapted to receive and measure wavelengths and intensities of visiblelight fluoresced by the fluid in response to UV light emitted by thelight source 310. In one or more embodiments, the detector 312 may beconfigured to output a signal proportional to an intensity of one ormore wavelengths of IR or visible light received at the detector 312.The output signal of the detector 312 may be indicative of thewavelength and intensity of the IR or visible light received at thedetector 312.

The detector 312 may include a single detector capable of detecting IRand visible spectrum light. The detector 312 may additionally includemultiple detectors, each detector 312 capable of detecting wavelengthswithin specific wavelength ranges of IR or visible light. In one or moreembodiments, the detector 312 may have an IR portion for detecting IRlight and a visible portion for detecting visible light. The detector312 may be configured to simultaneously detect the wavelengths andintensities of IR light and the wavelengths and intensities of visiblelight. In one or more embodiments, the detector 312 may include aplurality of photo diodes, at least one photo diode for detecting IRlight and at least one photo diode for detecting visible light. In oneor more embodiments, the detector 312 may include a single photo diode,and one or more optical and/or mathematical filters may be used toenable the single photo diode to measure the wavelengths and intensitiesfor both IR and visible light. In one or more embodiments, the detector312 may include one photo diode for detecting IR light and a pluralityof photo diodes for detecting visible light. Each of the visible lightphoto diodes may correspond to a specific range of wavelengths ofvisible light. In one or more embodiments, the detector 312 may have atleast three photo diodes for detecting visible light: at least one redspectrum diode for detecting red wavelengths of visible light, at leastone green spectrum diode for detecting green wavelengths of visiblelight, and at least one blue spectrum diode for detecting bluewavelengths of visible light. In one or more embodiments, the detector312 may have at least six photo diodes, one photo diode for each of red,orange, yellow, green, blue, and violet spectra ranges of visible light.In one or more embodiments, the detector 312 may be an imaging systemadapted to measure the wavelengths and intensity of IR and/or visiblelight.

Various combinations of light sources, detectors, and/or filters may beutilized to focus the OFS 130 on one or more specific wavelength rangesof light. In one or more embodiments, the light source 310 may be asingle white light, and the detector 312 may include a plurality ofdetecting elements, such as a plurality of photo diodes, each of whichis configured to measure the intensity of light in a specific wavelengthrange. In one or more embodiments, the light source 310 may be a singlewhite light, and one or more optical filters may be utilized andinterchanged to filter the light returning to the detector so that onlycertain wavelengths of light are received by the detector. In one ormore embodiments, the light source 310 may be a single white light, andone or more mathematical filters may be utilized by the OFS controller402 (FIG. 6) to filter the signal received from the detector 312 toreceive data only for the one or more specific wavelength ranges. In oneor more embodiments, the light source 310 may include a plurality oflight emitting devices, each capable of emitting light in a specificwavelength range, and the detector 312 may be a single detector todetect the specific wavelength ranges of light emitted by the pluralityof light emitting devices of the light source 310.

Referring to FIGS. 2 and 3, the detector 312 may include a UV filter 340to protect the detector 312 from exposure to UV light from the lightsource 310. For a detector 312 having photo diodes, the detector 312 maybe sensitive to UV light. As explained subsequently in this disclosure,the OFS 130 may measure the visible light fluoresced by the fluid in thechamber 306. When operating to measure the wavelengths and intensitiesof visible light fluoresced by the fluid, the detector 312 may besimultaneously exposed to UV light emitted by the light source 310 andvisible light fluoresced by the fluid in the chamber 306 in response tothe UV light. The UV filter 340 may be used to prevent exposure of thedetector 312 to the UV light while simultaneously allowing the visiblelight to penetrate and irradiate the detector 312 for measurement of thewavelengths and intensities of visible light fluoresced by the fluid.The UV filter 340 may be a coating or film applied directly to a surface342 (FIG. 2) of the detector 312 or may be a separate UV filter lenspositioned between the detector 312 and the chamber 306 such thatoptical communication between the chamber 306 and the detector 312passes through the UV filter lens. In one or more embodiments, the OFS130 may include a filter lens housing 344 (FIG. 3) disposed around theUV filter 340. The filter lens housing 344 may prevent UV light frombypassing or going around the UV filter 340 to reach the detector 312.

Both the light source 310 and the detector 312 may be optically coupledto the chamber 306 defined in the sensor housing 304 such that the lightsource 310 and the detector 312 are in optical communication with thefluid disposed within the chamber 306. The light source 310 may beoptically coupled with the chamber 306 so that, when the fluid isdisposed within the chamber 306, the light emitted by the light source310 passes into the chamber 306 and through the fluid disposed withinthe chamber 306. The detector 312 may be optically coupled to thechamber 306 so that, when fluid is disposed within the chamber 306, thedetector 312 may receive light passing through the fluid in the chamber306 or visible light fluoresced by the fluid in the chamber 306 inresponse to the UV light emitted by the light source 310. In one or moreembodiments, the light source 310, the detector 312, or both may bedisposed within the chamber 306 and may be in direct contact with thefluid disposed within the chamber 306. Referring to FIGS. 2 and 3, inone or more embodiments, the light source 310, detector 312, or both maybe fluidly isolated from the fluid in the chamber 306 by a transparentmember. The transparent member may allow light from the light source 310to pass through into the fluid, but may prevent the fluid fromcontacting the light source 310 and/or the detector 312. The transparentmember may be one or more windows 346. The window 346 may be plastic,glass, or other material that is generally transparent to at least IR,visible, and UV light. In one or more embodiments, the window 346 maynot substantially impede the light traveling through the window 346,which impedence may influence the wavelengths and intensities of thelight received and measured by the detector 312. In one or more otherembodiments, the OFS controller 402 (FIG. 6) may include one or morealgorithms for correcting the wavelength and intensity information forthe light received by the detector 312 for any effects caused by thelight passing throughout the window 346. In one or more embodiments, thewindow 346 may be Pyrex® brand glass by Corning Incorporated. The window346 may allow IR, visible, and UV light to pass through the window 346such that the light source 310 and the detector 312 remain in opticalcommunication with the chamber 306 while at the same time being fluidlyisolated from the fluid in the chamber 306. One or more sealing members348 may be disposed between the window 346 and the body 302 of the OFS130 to maintain a fluid tight seal to fluidly isolate the light source310 and detector 312 from the fluid in the chamber 306.

Referring to FIGS. 4A-4C, the light source 310 and the detector 312 maybe positioned at or adjacent to a first side 350 of the chamber 306 suchthat both the light source 310 and the detector 312 are opticallycoupled to the chamber 306 from the same side of the chamber 306. Areflector 330 may be positioned at or adjacent to a second side 352 ofthe chamber 306 opposite from the light source 310 and the detector 312.The reflector 330 may be positioned so that the reflector 330 reflectsthe light emitted into the chamber 306 by the light source 310 towardsthe detector 312. The arrows 335 in FIGS. 4A-4C denote the flow of fluidthrough apertures 308 into and out of the chamber 306. As shown in FIGS.4A and 4B, which illustrate the light source 310 and detector 312positioned at the same side (first side 350) of the chamber 306, whenfluid is disposed within the chamber 306, at least a portion of thelight (e.g., visible or IR) emitted from the light source 310 passesinto the chamber 306, travels through the fluid disposed in the chamber306, reflects off of the reflector 330, travels back through the fluidin the chamber 306 to the detector 312, where the emitted light isreceived by the detector 312.

An optical communication pathway 332 may be defined as a path of travelof the light from the light source 310, through the fluid disposedwithin the chamber 306, and to the reflector 330, and then from thereflector 330, back through the fluid in the chamber 306, and to thedetector 312. When the fluid is disposed within the chamber 306, the IRand visible light may pass into and through the fluid in the chamber 306when traveling along the optical communication pathway 332 from thelight source 310 to the detector 312. In one or more embodiments, thefirst side 350 of the chamber 306, at or adjacent to which the lightsource 310 and detector 312 are disposed, may be positioned closer tothe electronics portion 318 of the body 302 and may be oriented to facegenerally toward the sensor end 314 of the body 302, and the second side352 of the chamber 306 may be positioned between the sensor end 314 ofthe body 302 and the chamber 306 and may face generally towards thefirst side 350 of the chamber 306 (i.e., towards the electronics portion318 of the body 302). In one or more embodiments, the light source 310and detector 312 may be on the same side (i.e., the first side 350) ofthe chamber 306, and the chamber 306 may be an open-sided chamberwithout a second side 352 (i.e., without a reflector) so that the lightis emitted from the light source 310 into the fluid and the detector 312detects light reflected by the fluid.

Referring to FIGS. 5A and 5B, in one or more embodiments, the lightsource 310 may be positioned at or adjacent to the second side 352 ofthe chamber 306, and the detector 312 may be positioned at or adjacentto the first side 350 of the chamber 306 such that the detector 312 andthe light source 310 are positioned facing one another. The second side352 of the chamber 306, at or adjacent to which the light source 310 ispositioned, may be directly opposite the first side 350 of the chamber306 such that, when the fluid is disposed within the chamber 306, lightemitted from the light source 310 travels along a generally linear path334 from the light source 310, through the fluid in the chamber 306, andto the detector 312. A supplemental window 347 may be positioned betweenthe light source 310 and the chamber 306 to fluidly isolate the lightsource 310 from the fluid in the chamber 306. The arrows 335 in FIGS.5A-5C denote the flow of fluid through apertures 308 into and out of thechamber 306. With the light source 310 positioned at the second side 352opposite the detector 312 and the fluid disposed within the chamber 306,light emitted by the light source may travel along a generally linearpath 334 from the light source 310, through the fluid, and to thedetector 312. In one or more embodiments, the detector 312 may bepositioned at or adjacent to the second side 352 of the chamber 306, andthe light source 310 may be positioned at or adjacent to the first side350 of the chamber 306. In one or more embodiments, the light source 310or the detector 312 may be positioned at or adjacent to a third side 354of the chamber 306, which may be oriented at an angle relative to thefirst side 350, and one or more reflectors 330 may be positioned withinor in optical communication with the chamber 306 to reflect IR and/orvisible light from the light source 310 to the detector 312. In one ormore embodiments, a plurality of reflectors 330 may be positioned withinor in optical communication with the chamber 306 to redirect lightemitted from the light source 310 to the detector 312.

Referring back to FIG. 2, the reflector 330 may be optically coupled tothe chamber 306 so that light from the light source 310 or visible lightfluoresced by the fluid in response to UV light from the light source310 may contact and be reflected from a reflective surface 331 of thereflector 330. The reflector 330 may be positioned within the chamber306 and in contact with the fluid disposed within the chamber 306. Inone or more embodiments, the reflector 330 may include a chemical and/orsolvent resistant material in contact with the fluid in the chamber 306.In one embodiment, the reflector 330 may have a reflective surface 331that may be a polytetrafluoroethylene, such as Teflon™, which isproduced and marketed by The Chemours™ Company. Alternatively, thereflector 330 may be fluidly isolated from the chamber 306 by areflector window (not shown). The reflector window may allow light topass through to maintain optical communications between the reflector330 and the chamber 306 while simultaneously fluidly isolating thereflector 330 from the fluid disposed within the chamber 306. Thereflector 330 may be removably coupled to the sensor end 314 of the body302 by a snap ring 360, end cap (not shown), or other coupling means. Asealing member 362, such as a gasket or o-ring, may be disposed betweenthe reflector 330 and the sensor housing 304.

Referring to FIGS. 2 and 3, the OFS 130 may include an electronicsholder 370 positioned within the electronics portion 318 of the body302. The electronics holder 370 may define an electronics compartment372, which may be a generally cylindrical hollow cavity, within theelectronics holder 370. One or more electronic components, such as acircuit board 374 (FIG. 3), the light source 310 (FIG. 2), the detector312 (FIG. 2), other electronic component, or combinations of these, forexample, may be disposed within the electronics compartment 372 in theelectronics holder 370. The electronics compartment 372 may be fluidlyisolated from the chamber 306 in the sensor housing 304 such that fluidfrom the chamber 306 does not contact the electronic componentscontained within the electronics compartment 372. In one or moreembodiments, the electronics compartment 372 may be fluidly isolatedfrom the chamber 306 by the window 346 and the sealing members 348. Inone or more embodiments, the electronics holder 370 may include a spacer375 (FIG. 3) to position the one or more electronic components withinthe electronics compartment 372.

Referring to FIGS. 2 and 3, an end cap 376 may be removeably coupled toan end 378 of the body 302, the end 378 being generally opposite fromthe sensor end 314 of the body 302. The end cap 376 may maintain theelectronics holder 370 and electrical components within the body 302 ofthe OFS 130. The end cap 376 may have an electrical fitting 380 forpassing one or more electrical cables 382 through the end cap 376 to theelectrical components. The electrical cables 382 may include a powersupply cable and one or more electronic communication cables. The OFS130 may include one or more seal members 362 to maintain a fluid-tightseal around the electronics holder 370 to fluidly isolate theelectronics compartment 372 from fluid intrusion. The OFS 130 may alsoinclude a retaining ring 384 disposed between the end cap 376 and theelectronics holder 370.

Referring now to FIG. 6, an optical sensor system 400 may include thelight source 310 and detector 312 of the OFS 130 and an OFS controller402, which may include at least one processor 410 and at least onememory module 420 communicatively coupled to the processor 410. In oneor more embodiments, the OFS controller 402, including the processor 410and memory module 420, may be disposed on the circuit board 374 (FIG. 3)positioned within the electronics holder 370 (FIG. 3). The OFScontroller 402 may be communicatively coupled with the light source 310to provide a control signal to the light source 310. The OFS controller402 may be communicatively coupled with the detector 312 to receive thewavelength and intensity information or an output signal indicative ofthe wavelength and intensity of received light from the detector 312.The OFS controller 402 may also be communicatively coupled with a systemcontroller 70 (FIG. 10) and may receive control signals from andtransmit information to the system controller 70. Communication betweenthe OFS controller 402 and/or the OFS 130 itself and the systemcontroller 70 (FIG. 10) may be through one or more wired, wireless, oroptical communication. The optical sensor system 400 may optionallyinclude an OFS display 424, which may be communicatively coupled to theOFS controller 402. In one or more embodiments, the OFS display 424 maybe positioned externally relative to the body 302 of the OFS 130 and maybe communicatively coupled to the OFS controller 402 by one or more ofthe electrical cables 382 (FIG. 3).

The optical sensor system 400 may also include one or more temperaturesensors 430. The temperature sensors 430 may be positioned in theelectronics holder 370 (FIG. 3) to measure a temperature of theelectronic components or may be positioned in the chamber 306 to measurea fluid temperature. In one or more embodiments, at least one of thetemperature sensors 430 may be coupled to the circuit board 374 of theOFS 130 so that the temperature sensor 430 measures the temperature ofthe electronic components, which may include one or more of the lightsource 310, detector 312, OFS controller 402, processor 410, memorymodules 420, other electronic components, or combinations of these. Inone or more embodiments, the temperature sensor 430 may be apiezoelectric temperature sensor. In one or more embodiments, thetemperature sensor 430 may be a chip coupled to the circuit board 374.In one or more embodiments, one of the temperature sensors 430 may bepositioned within the chamber 306 to measure the fluid temperature whenthe fluid is disposed within the chamber. In one or more embodiments,the OFS 130 may have at least one temperature sensor 430 positionedwithin the electronics holder 370 to measure a temperature of theelectronics and at least one temperature sensor (not shown) positionedwithin the chamber 306 of the sensor housing 304 to measure the fluidtemperature. Each of the one or more temperature sensors 430 may becommunicatively coupled with the OFS controller 402 for communicatingtemperature information to the OFS controller 402.

The one or more memory modules 420 may have one or more fluid profilesfor one or more fluids (e.g., liquid products) stored therein. The fluidprofiles may be in the form of one or more look-up tables (LUT). Thefluid profiles stored in the memory modules 420 may be indexed by fluidtype. Each fluid profile may include a transmissivity profile for aspecific fluid. The transmissivity profile may include information onthe wavelengths and intensities of visible light transmitted through thefluid or reflected by the fluid. In one or more embodiments, each fluidprofile may include a plurality of transmissivity profiles for thefluid, with each transmissivity profile providing transmissivityinformation for a specific temperature of the light source 310, fluidtemperature, or both. In addition or in the alternative, each fluidprofile may include a light absorption profile for the fluid, theabsorption profile including information on the wavelengths andintensities of light absorbed by the fluid. Each fluid profile may alsoinclude a fluorescence profile, which may include information on thewavelengths and intensities of visible light fluoresced by the fluid inresponse to UV light. In one or more embodiments, each fluid profile mayinclude a plurality of fluorescence profiles for the fluid, eachfluorescence profile including fluorescence information for a specifictemperature of the light source 310, fluid temperature, or both. In oneor more embodiments, the fluid profile may include a color of the fluid.The color of the fluid may be expressed as the wavelengths andintensities of visible light reflected by the fluid when exposed tovisible light. In one or more embodiments, the memory modules 420 mayinclude fluid profiles for specific liquid products that are expected tobe encountered by the OFS 130. In one or more embodiments, the memorymodule 420 may include a temperature algorithm for adjusting datareceived from the detector 312 to account for changes in the temperatureof the electronics, fluid temperature, or both. The memory modules 420may also have machine readable instructions stored thereon that, whenexecuted by the processor 410, cause the OFS controller 402 to operatethe OFS 130 to determine a fluid type of the fluid in the chamber 306 orto determine whether a fluid is in the chamber 306.

Referring back to FIGS. 4A-4C, the OFS 130 may be used to determinewhether a fluid is present in the chamber 306 and to determine a fluidtype of the fluid in the chamber 306 based on the visible lighttransmitted through the fluid, the visible light fluoresced by the fluidin response to UV light, or both. The OFS 130 may be utilized todetermine the fluid type for many different liquid products, such aspetroleum-based fuels (e.g., diesel fuel, gasoline, kerosene), organicsolvents, oils, resins, aqueous solutions, other fluids, or combinationsof fluids. In one or more embodiments, the fluid may be a liquid productthat is a petroleum-based fuel, and the OFS 130 may be used to determinea type of petroleum-based fuel, which may include diesel fuels, fuelswith differing octane numbers, fuels having varying concentrations ofone or more alcohols, fuels containing one or more dyes, or other fuels.In one or more embodiments, the fluid may be a vapor or gas, such asfuel gas or natural gas, for example.

Referring to FIGS. 4A and 5A, the OFS 130 may use IR light to determinewhether a fluid is present in the chamber 306 of the sensor housing 304.FIG. 4A schematically depicts an embodiment of the OFS 130 in which thelight source 310 and the detector 312 are positioned on or adjacent tothe same side (first side 350) of the chamber 306 with the reflector 330positioned on the opposite side (second side 352) of the chamber 306.The OFS controller 402 (FIG. 6) may send a signal to the light source310 to cause the light source 310 to emit IR light into the chamber 306,which then may cause the light source 310 to emit the IR light into thechamber 306. The IR light may be emitted by an IR portion of the lightsource 310. The IR light travels along an optical communication pathway332, along which the IR light travels through the chamber 306, reflectsoff of the reflector 330 positioned on the opposite side (second side352) of the chamber 306, travels back through the chamber 306, and isreceived by the detector 312, which measures the intensity of the IRlight received. The intensity of the IR light may be measured by an IRportion of the detector 312. FIG. 5A illustrates an embodiment in whichthe light source 310 is positioned on an opposite side (second side 352)of the chamber 306 from the detector 312. In this embodiment, the IRlight emitted by the light source 310 travels along a generally linearpath 334 through the fluid in the chamber 306 and to the detector 312.

Certain fluids, such as petroleum-based fuels for example, absorb IRlight. When a fluid is present in the chamber 306, the fluid may absorbsome of the IR light traveling through the fluid. The remaining IR lightpasses through the fluid and reaches the detector 312. Because some ofthe IR light is absorbed, less IR light reaches the detector 312compared to the intensity of the IR light emitted by the light source310. When a fluid is present in the chamber 306, the intensity of the IRlight received by the detector 312 may be substantially less than the IRlight emitted by the light source 310 into the chamber 306. Therefore, asubstantial decrease in the intensity of the IR light from the lightsource 310 to the detector 312 may indicate that fluid is disposedwithin the chamber 306. The memory modules 420 (FIG. 6) may include oneor more IR threshold intensities, which are less than the intensity ofthe IR light emitted by the light source 310. In one or moreembodiments, the memory modules 420 may store a threshold intensity foreach fluid type as part of the fluid profile for each fluid type. TheOFS controller 402 may compare the intensity of IR light measured by thedetector 312 to the IR threshold intensities stored in the memorymodules 420. An intensity of IR light measured by the detector 312 thatis less than the IR threshold intensity stored in the memory modules 420may indicate the presence of a fluid in the chamber 306. As used herein,a “substantial decrease in intensity” of the IR light refers to adecrease in the intensity of the IR light from the intensity of the IRlight emitted from the light source 310 to an intensity of IR lightreceived by the detector 312 that is less than the IR thresholdintensity. When a fluid is not present in the chamber 306, the intensityof IR light measured by the detector 312 may be generally the same oronly slightly different than the intensity of the IR light emitted bythe light source 310 due to the absence of a fluid that absorbs the IRlight.

Changes in the temperature of the electronics compartment 372 (FIG. 3)and the light source 310 disposed therein may influence the intensity ofthe IR light emitted by the light source 310. Additionally, changes inthe fluid temperature in the chamber 306 may influence the absorption ofIR light by the fluid in the chamber 306. The OFS controller 402 (FIG.6) may receive a temperature signal from the one or more temperaturesensors 430 (FIG. 6) which may be indicative of the temperature of theelectronics, fluid temperature, or both. The OFS controller 402 mayadjust the intensity of IR light received by the detector 312, thethreshold intensity retrieved from the memory modules 420, or both toaccount for differences in the temperature of the electronics, fluidtemperature, or both.

In one or more embodiments, the OFS 130 may use visible light emitted bythe light source 310, instead of IR light, to determine whether a fluidis in the chamber 306. The OFS 130 may use one or more specificwavelengths of visible light emitted by the light source 310 todetermine whether a fluid is in the chamber 306. In one or moreembodiments, the OFS 130 may include a secondary sensor (not shown) fordetermining whether fluid is present in the chamber 306. In one or moreembodiments, the secondary sensor may be a wet-dry sensor.

In one or more embodiments, the OFS 130 may emit IR or visible lightinto the chamber 306 to determine whether fluid is present in thechamber 306 at periodic time intervals during operation. The OFScontroller 402 (FIG. 6) may generate a “fluid present” message when theOFS 130 detects fluid in the chamber 306 and a “no fluid present”message when the OFS 130 does not detect a fluid in the chamber 306. Inone or more embodiments, the OFS controller 402 may set a fluid presentparameter to a fluid present value or to a no fluid present value andmay store the fluid present parameter in the memory modules 420. Inembodiments, the system controller 70 (FIG. 6) may query or poll thememory modules 420 of the OFS controller 402 to retrieve the fluidpresent parameter. In one or more embodiments, the OFS 130 may determinewhether fluid is in the chamber 306 as a precondition to emittingvisible light or UV light into the chamber 306 for determining a fluidtype of the fluid in the chamber 306.

A determination by the OFS 130 that no fluid is present in the chamber306 may indicate that a storage tank or tank compartment 25 (FIG. 9) isempty of liquid product or that no liquid product is flowing through atransfer pipe or conduit, which may indicate one or more conditions,such as the tank or tank compartment being empty, one or more valvesbeing closed, or other condition. In one or more embodiments, the OFS130 may be used to provide an indication of when an operation iscompleted. the OFS 130 may monitor whether fluid is in the chamber 306throughout an operation, such as unloading the tank compartment 25 (FIG.9) of a product transport vehicle 15 (FIG. 9) for example, to determinewhen an operation may be completed or nearing completion. A change instatus from a “fluid present” in the chamber 306 status to a “no fluidpresent” in the chamber 306 status may indicate that a tank compartmentis empty or that no more fluid is flowing through the transfer pipe,conduit or control valve. In one or more embodiments, the OFS controller402 may generate the “no fluid present” message or change the fluidpresent parameter to a no fluid present value, which may indicate thatthe operation is complete. The OFS controller 402 may save and/ortransmit the fluid present parameter, the “no fluid present” message, orthe “fluid present” message to the system controller 70 or to the OFSdisplay 424. In one or more embodiments, the OFS controller 402 mayoutput a fluid present signal indicative of a fluid present in thechamber 306. The fluid present signal indicative of a fluid present inthe chamber 306 may be received by the system controller 70. Thepresence or absence of the fluid present signal may cause the systemcontroller 70 to determine whether a tank is empty or whether anoperation, such as a transfer operation is complete.

Referring to FIG. 4B, the OFS 130 may use visible light to determine afluid type of the fluid in the chamber 306. FIG. 4B schematicallyillustrates an embodiment of the OFS 130 in which the light source 310and the detector 312 are positioned at or adjacent to the same side(first side 350) of the chamber 306. The OFS controller 402 (FIG. 6) maysend a signal to the light source 310 to cause the light source 310 toemit visible light into the chamber 306. In response, the light source310 emits the visible light into the chamber 306. The visible light maybe emitted by a visible light portion of the light source 310. In one ormore embodiments, the light source 310 may include a plurality ofvisible spectra LEDs, each LED configured to emit a range of wavelengthsof visible light. In one or more embodiments, each visible spectra LEDmay be flashed (i.e., activated for a period of time and thendeactivated) in series such that only one wavelength range of visiblelight is emitted into the chamber 306 at any point in time. The visiblelight may travel along the optical communication pathway 332, alongwhich the visible light may travel through the fluid in the chamber 306,reflect off of the reflector 330 positioned on the opposite side (secondside 352) of the chamber 306, travel back through the fluid in thechamber 306, and is received by the detector 312, which may measure thewavelengths and intensities of the visible light received by thedetector 312. The wavelengths and intensities of the visible light maybe measured by a visible light portion of the detector 312. FIG. 5Billustrates an embodiment in which the light source 310 is positioned onan opposite side (second side 352) of the chamber 306 from the detector312. In this arrangement, the visible light emitted by the light source310 travels along a generally linear path 334 through the fluid in thechamber 306 to the detector 312.

Different types of fluids, such as petroleum-based fuels for example,absorb different wavelengths of visible light passing through the fluid.The visible light that is not absorbed by the fluid may pass through thefluid and reach the detector 312. An intensity of a specific wavelengthof visible light measured by the detector 312 that is substantially lessthan the intensity of that specific wavelength of visible light emittedfrom the light source 310 may indicate that the fluid in the chamber 306absorbs that specific wavelength of visible light. Additionally,different types of fluids, such as petroleum-based fuels for example,may reflect different wavelengths of visible light emitted into thefluid. As non-limiting examples, diesel fuels may be slightly ambercolor or may include a colored dye, which indicates that diesel fuelsmay reflect yellow wavelengths of light or wavelengths of lightassociated with the color of the dye, and kerosene may be generallyclear or colorless, which may indicate that kerosene reflects verylittle visible spectra light. Various grades of gasoline may reflectvarious wavelengths of visible light, which may result in variations inthe intensity of specific wavelengths of visible light detected by thedetector 312. The visible light reflected by the fluid in the chamber306 may also be reflected back towards the detector 312 and maycontribute to the wavelengths and intensities of the visible lightmeasured by the detector 312. Because each fluid may absorb and reflectdifferent wavelengths of visible light, measurement of the wavelengthsand intensities of visible light reaching the detector 312 may provideinformation on the visible light absorbed and/or reflected by the fluid,which information may provide characteristics with which to identify thefluid type of the fluid in the chamber 306.

The detector 312 may receive the visible light, and the OFS controller402 may process the wavelength and intensity information for the visiblelight received by the detector 312 and may compare the wavelength andintensity information for the received visible light to the one or morefluid profiles stored in the one or more memory modules 420. Asdescribed previously in this disclosure, the fluid profiles may be inthe form of a plurality of LUTs and may include visible lighttransmissivity profiles for one or more fluids. The OFS controller 402may determine a fluid type of the fluid in the chamber 306 based on thecomparison of the wavelength and intensity of the visible light receivedby the detector 312 to the plurality of fluid profiles.

Temperature may influence the wavelengths and intensities of visiblelight emitted by the light source 310. Temperature may also influencethe intensities of IR and UV light emitted by the light source 310. As anon-limiting example, the light source 310 may include one or more LEDs,which may experience changes in output brightness with changes intemperature. These changes in LED brightness may then affect theintensity of visible light received by the detector 312. Changes intemperature may also affect the absorption and reflection of visiblelight by the fluid disposed in the chamber 306, which may also influencethe wavelengths and intensities of visible light measured by thedetector 312. The OFS controller 402, therefore, may receive atemperature of the electronics, fluid temperature in the chamber 306, orboth from one or more temperature sensors 430 and may adjust thewavelength and intensity information determined for the light receivedby the detector 312 or the fluid profiles stored in the memory modules420 based on the temperature of the electronics, fluid temperature, orboth. In one or more embodiments, the OFS controller 402 may utilize analgorithm stored in the memory modules 420 to mathematically adjust thewavelength and intensity information determined for the light receivedby the detector, the fluid profiles stored in the memory modules 420, orboth to account for changes in the temperature of the electronics, fluidtemperature, or both. In one or more embodiments, the memory modules 420may include a plurality of fluid profiles for each fluid type, each ofthe plurality of fluid profiles providing the transmissivity profile,fluorescence profile, and other fluid profile information over a rangeof electronics temperatures, fluid temperatures, or both. The OFScontroller 402 may compare the wavelength and intensity information forthe light received by the detector 312 to the fluid profiles at aspecific temperature, as indicated by the temperature sensors 430. Inone or more embodiments, the memory modules 420 may include LUTs ofintensity versus temperature for each wavelength of light for eachfluid.

Additionally, the OFS controller 402 may use one or more mathematicalfilters to limit the wavelength and intensity information determined forthe light received from the detector 312 to narrower ranges ofwavelengths. The mathematical filters enable the OFS controller 402 tofocus on specific ranges of wavelength of visible light, which may beexpected to provide distinguishing characteristics of the fluid.

In some cases, measurement of the wavelengths and intensities of visiblelight transmitted through the fluid may not be sufficient to adequatelydistinguish between two or more different types of fluids. As anon-limiting example, gasoline grades having different octane ratingsmay absorb and reflect similar wavelengths of visible light such thatmeasuring the wavelengths and intensities of visible light passingthrough the gasoline grades may not enable the OFS controller 402 toconfidently distinguish between the different octane grades of thegasoline. Liquid products, such as different octane grades of gasolineand different grades of diesel fuel for example, may have certaincomponents, such as certain hydrocarbon components or dye components forexample, that may fluoresce different wavelengths of visible light whenexposed to UV light.

Referring to FIG. 4C, the OFS 130 may measure the wavelengths andintensities of visible light fluoresced by the fluid in the chamber 306in response to UV light emitted by the light source 310 to furthercharacterize and identify a fluid type of the fluid in the chamber 306.FIG. 4C schematically illustrates an embodiment of the OFS 130 in whichthe light source 310 and the detector 312 are positioned at or adjacentto the same side (first side 350) of the chamber 306. In one or moreembodiments, the OFS 130 may include one or more light sources 310positioned within the chamber 306. FIG. 4C denotes UV light withreference number 394 and fluoresced visible light by reference number396. The OFS controller 402 (FIG. 6) may send a control signal to thelight source 310 to cause the light source 310 to emit UV light 394 intothe chamber 306. In response, the light source 310 emits the UV light394 into the chamber 306. The UV light 394 may be emitted by a UVportion of the light source 310. In one or more embodiments, the lightsource 310 does not emit visible light into the chamber 306simultaneously with emitting the UV light 394.

When a fluid is disposed within the chamber 306, the UV light 394 maytravel into the chamber 306 and into the fluid. The UV light 394 maycause the fluid, or one or more components of the fluid, to fluoresceand emit fluoresced visible light 396 into the chamber 306. Thefluoresced visible light 396 may be emitted from the fluid in aplurality of directions. A portion of the fluoresced visible light 396may travel back through the fluid to the detector 312, and anotherportion of the fluoresced visible light 396 may travel through thefluid, reflect off of the reflector 330, and travel back through thefluid to the detector 312. The fluoresced visible light 396 may bereceived at the detector 312, which may measure the wavelengths andintensities of the fluoresced visible light 396. The wavelengths andintensities of the fluoresced visible light 396 may be measured by thevisible light portion of the detector 312. FIG. 5C illustrates anembodiment in which the light source 310 is positioned at an oppositeside (second side 352) of the chamber 306 from the detector 312. In thisembodiment, the UV light 394 emitted by the light source 310 travelsinto the fluid disposed in the chamber 306. Upon exposure to the UVlight 394, the fluid, or a component thereof, fluoresced visible light396, which travels in a plurality of directions. At least a portion ofthe fluoresced visible light 396 travels towards and is received at thedetector 312. The OFS controller 402 may process the received light todetermine wavelength and intensity information for the received light.

One or more components of the fluid may fluoresce visible light withinone or more specific wavelength ranges when the component is exposed tothe UV light 394. Different fluid types may have different componentsthat fluoresce different wavelengths and intensities of fluorescedvisible light 396, and these different wavelengths and intensities offluoresced visible light 396 may provide identifying characteristics fordetermining the fluid type of the fluid in the chamber 306. As describedabove, the one or more fluid profiles stored in the memory modules 420(FIG. 6) may include the fluorescence profiles for the one or morefluids, the fluorescence profiles including wavelengths and intensitiesof fluoresced visible light 396 expected to be fluoresced by thecomponents in the fluids. The OFS controller 402 may compare theinformation on the wavelengths and intensities of fluoresced visiblelight 396 received from the detector 312 to the fluorescence profiles inthe one or more fluid profiles to further determine a fluid type of thefluid in the chamber 306. As discussed above, the OFS controller 402 mayalso adjust the wavelength and intensity information for the fluorescedvisible light 396 received by the detector 312 or the fluorescenceinformation in the fluid profiles by the temperature of the electronics,a fluid temperature, or both prior to making the comparison anddetermining the fluid type of the fluid. In one or more embodiments, thefluid profiles in the memory modules 420 may include fluorescenceprofiles at various temperatures for each fluid and the OFS controller402 may select the fluorescence profiles associated with the temperatureof electronics, fluid temperature, or both to compare to the informationreceived from the detector 312. As discussed previously, the OFScontroller 402 may also utilize one or more mathematical filters tofilter the information received from the detector 312 to one or morespecific wavelength ranges of visible light expected to be fluoresced bythe fluids.

In one or more embodiments, the OFS controller 402 may determine thefluid type of the fluid in the chamber 306 based on the wavelengths andintensities of visible light transmitted through the fluid. In one ormore embodiments, the OFS controller 402 may determine the fluid type ofthe fluid in the chamber 306 based on the wavelengths and intensities ofvisible light fluoresced by the fluid, or one or more components of thefluid, in response to UV light. In one or more embodiments, the OFScontroller 402 may determine the fluid type of the fluid in the chamber306 based on both the wavelengths and intensities of visible lighttransmitted through the fluid and the wavelengths and intensities ofvisible light fluoresced by the fluid, or a component thereof, inresponse to UV light. In one or more embodiments, the OFS 130 maysimultaneously emit IR light and visible light into the chamber 306 tosimultaneously determine whether fluid is present in the chamber 306 andmeasure the wavelengths and intensities of visible light transmittedthrough the fluid.

Referring back to FIG. 6, once the OFS controller 402 has determined afluid type of the fluid in the chamber 306, the OFS controller 402 maygenerate and save a fluid type in the memory modules 420. In one or moreembodiments, the OFS 130 may be installed on a product transport vehicle15 and the fluid type may be a transported liquid type. In one or moreother embodiments, the OFS 130 may be installed in a storage tank ordistribution tank such that the fluid type may be a stored liquid type.The OFS controller 402 may transmit the fluid type (i.e., as thetransported liquid type or stored liquid type depending on where the OFS130 is installed) to the system controller 70 (FIGS. 6 and 10). In oneor more embodiments, the system controller 70 may query or poll thememory modules 420 of the OFS controller 402 to retrieve the fluid type(i.e., as the transported liquid type). In one or more embodiments, theOFS 130 may be configured to output a fluid type signal indicative of afluid type of the fluid in the chamber 306, and the system controller 70of the crossover protection system may determine a transported liquidtype based on the fluid type signal output from the OFS 130. If the OFScontroller 402 is unable to identify the fluid type of the fluid in thechamber based on the visible light transmitted or the visible lightfluoresced in response to exposure to UV light, then the OFS controller402 may generate an “unknown fluid” or “unknown fluid type” message orsignal. The OFS controller 402 may save the “unknown fluid” message inthe memory modules 420 and/or may transmit the “unknown fluid” messageto the system controller 70. In one or more embodiments, the OFScontroller 402 may set the fluid type to a value indicative of anunknown fluid type when the OFS controller 402 is unable to determinethe fluid type of the fluid in the chamber 306.

The OFS 130 and optical sensor systems 400 disclosed herein may becapable of differentiating between different types of fluids that havesimilar physical and chemical properties, the similar properties causingthe two different types of fluids to be indistinguishable to existingfluid property sensors. In one or more embodiments, the OFS 130 may becapable of distinguishing between different octane grades of gasolineand determining a fluid type for each separate grade. In one or moreembodiments, the OFS 130 may be capable of distinguishing betweendifferent grades of dyed diesel fuels. The OFS 130 may be capable ofdistinguishing between a wide range of fluids that are liquids, such aspetroleum-based fuels (e.g., diesel fuel, gasoline, and kerosene),organic solvents, resins, aqueous solutions, or other materials. In oneor more embodiments, the OFS 130 may be capable of distinguishingbetween one or more fluids that are vapors or gases. In one or moreembodiments, the OFS 130 may also be capable of indicating when a tankis empty or when an operation, such as a material transfer operation, iscomplete.

Referring now to FIGS. 7-8, a method 500 for determining whether a fluidis present in the chamber 306 and a method 520 for determining a fluidtype of a fluid in the chamber 306 are schematically depicted. Althoughthe steps associated with the blocks of FIGS. 7-9 will be described asbeing separate tasks, in other embodiments, the blocks may be combinedor omitted. Further, while the steps associated with the blocks of FIGS.7-8 will be described as being performed in a particular order, in otherembodiments, the steps may be performed in a different order. Themachine readable instructions recited in the following discussion may bestored on the memory modules 420 and may be executed by the processor410.

Referring to FIG. 7, the method 500 for determining whether a fluid ispresent in the chamber 306 of the OFS 130 is schematically depicted. Atblock 502, machine readable instructions stored on the one or morememory modules 420, when executed by the processor 410, may cause theOFS 130, in particular the OFS controller 420, to transmit a controlsignal to the light source 310 to cause the light source 310 to emit IRlight or visible light into the chamber 306. In response to the controlsignal, the light source 310 may emit IR light or visible light into thechamber 306. In one or more embodiment, the control signal may instructthe light source 310 to emit IR light or visible light. In one or moreembodiments, the OFS controller 402 may cause the light source 310 toemit IR light into the chamber 306. The machine readable instructionsmay cause the OFS 130 to receive IR light or visible light at thedetector 312.

At block 504, the machine readable instructions, when executed, maycause the OFS 130 to measure an intensity of the IR or visible lightreceived at the detector 360. In one or more embodiments, the machinereadable instructions may cause the OFS 130 to receive IR or visiblelight at the detector. The OFS controller 402 may process the IR lightor visible light received at the detector to determine an intensity ofIR or visible light received by the detector 312. The OFS controller 402may save the intensity of IR or visible light information in the one ormore memory modules 420. The machine readable instructions, whenexecuted, may cause the OFS controller 402 to apply a mathematicalfilter to IR or visible light received at the detector 312.

In block 506, the machine readable instructions, when executed, maycause the OFS controller 402 to compare the intensity of the received IRlight or visible light to a threshold intensity of IR light or visiblelight, respectively. The processor 410 may query the memory modules 420to retrieve the threshold intensity, which may be stored in the memorymodules 420 in one or more LUTs. The machine readable instructions, whenexecuted, may cause the OFS controller 402 to adjust the wavelength andintensity information for the received IR or visible light or thethreshold intensity retrieved from the memory modules 420 based on thetemperature of the electronics, the fluid temperature, or both. In block508, the machine readable instructions, when executed, may cause the OFScontroller 402 to determine that a fluid is present if the intensity ofthe received IR light or visible light is less than the thresholdintensity of IR light or visible light. The OFS controller 402 maygenerate a “fluid present” or “no fluid present” message or set a fluidpresent parameter to a fluid present value or a no fluid present valueto indicate whether a fluid is present in the chamber 306.

Referring now to FIG. 8, the method 520 for determining a fluid type ofthe fluid in the chamber 306 is schematically depicted. In block 522,machine readable instructions, when executed, may cause the OFScontroller 402 to send or transmit a control signal to the light source310 to cause the light source 310 to emit visible light into the chamber306. In response to the control signal, the light source 310 may emitvisible light into the chamber 306. In block 524, the machine readableinstructions, when executed, may cause the OFS controller 402 to receivewavelength and intensity information for visible light received by thedetector 312. The wavelength and intensity information may be receivedfrom the detector 312 through the communicative coupling of the detector312 to the OFS controller 402. In one or more embodiments, the OFScontroller 402 may receive one or more signals indicative of wavelengthsand intensities of visible light received at the detector 312 from thedetector 312 and may process the signal from the detector 312 todetermine the wavelengths and intensities of received visible light. Thewavelength and intensity information for the received light may be savedin the one or more memory modules 420.

In block 526, the machine readable instructions, when executed, maycause the OFS controller 402 to receive a temperature signal from thetemperature sensor 430. In embodiments, the temperature sensor 430 maybe positioned in the electronics compartment 372 such that thetemperature signal may indicate a temperature of the electronics. Inother embodiments, the temperature sensor 430 may be positioned in thechamber 306 such that the temperature signal may indicate a fluidtemperature in the chamber 306. In other embodiments, the OFS controller402 may receive a first temperature signal from a temperature sensor 430in the electronics compartment 372 and a second temperature signal fromanother temperature sensor 430 positioned in the chamber 306. In block528, the machine readable instructions, when executed, may cause the OFScontroller 402 to adjust one or more fluid profiles stored in the memorymodules 420 or the wavelength and intensity information received fromthe detector 312 based on one or more temperature signals. To adjust thefluid profiles for temperature, the processor 410 may query the memorymodules 420 to retrieve one or more of the fluid profiles, which arestored in the memory modules 420. In one or more embodiments, the OFScontroller 402 may adjust both the fluid profiles and the wavelength andintensity information received from the detector 312 for changes intemperature.

In block 530, the machine readable instructions, when executed, maycause the OFS controller 402 to compare the wavelength and intensityinformation for the received visible light, which was received by thedetector 312, to the one or more fluid profiles stored in the one ormore memory modules 420. The OFS controller 402 may determine a fluidtype of the fluid in the chamber 306 based on the comparison of thewavelength and intensity information for the received visible light tothe one or more fluid profiles. The machine readable instructions, whenexecuted, may cause the OFS controller 402 to query the memory modules420 to retrieve one or more fluid profiles. In block 532, the machinereadable instructions, when executed, may cause the OFS controller 402to determine whether a fluid type is successfully identified by the OFScontroller 402. If the OFS controller 402 determines that it hassuccessfully identified a fluid type of the fluid, the machine readableinstructions, when executed, may cause the OFS controller 402 togenerate and transmit a liquid type, which is indicative of the fluidtype of the fluid in the chamber 306, to the system controller 70 and/orthe OFS display 424. In one or more embodiments, the OFS 130 may bepositioned in contact with a tank compartment 25 (FIG. 9) or controlvalve 45 (FIG. 9) of a product transport vehicle 15 (FIG. 9) such thatthe liquid type may be a transported liquid type. In one or moreembodiments, the OFS 130 may output a fluid type signal indicative ofthe fluid type, and the system controller 70 may receive the output fromthe OFS 130. If the OFS controller 402 determines that it has notdetermined the fluid type of the fluid in the chamber 306, then the OFScontroller 402 may generate and transmit an “unknown fluid type” messageto the system controller 70 or may proceed with measuring the UVfluorescence of the fluid in the chamber 306 (i.e., proceed to block 536of method 520) to further determine the fluid type.

In block 536, the machine readable instructions, when executed by theprocessor 410, may cause the OFS controller 402 to send a control signalto the light source 310 to cause the light source 310 to emit UV lightinto the chamber 306. In response to the control signal, the lightsource 310 may emit UV light into the chamber 306. In block 538, themachine readable instructions, when executed, may cause the OFScontroller 402 to receive wavelength and intensity information forvisible light fluoresced by the fluid (fluoresced visible light 396) andreceived by the detector 312. The wavelength and intensity informationmay be received from the detector 312 through the communicative couplingof the detector 312 to the OFS controller 402. In one or moreembodiments, the OFS controller 402 may receive the wavelengths andintensities of the received light directly from the detector 312. Inother embodiments, the OFS controller 402 may receive one or moresignals indicative of wavelengths and intensities of visible lightreceived at the detector 312 and may process the one or more signalsfrom the detector 312 to determine the wavelengths and intensities ofvisible light received by the detector 312. The wavelength and intensityinformation for the received visible light may be saved in the one ormore memory modules 420.

In block 540, the machine readable instructions, when executed, maycause the OFS controller 402 to receive a temperature signal from thetemperature sensor 430. As described previously, the temperature signalmay indicate the temperature of the electronics, the fluid temperaturein the chamber 306, or both. In one or more embodiments, OFS controller402 may use the temperature signal(s) from block 526 rather thanreceiving another temperature signal in block 540. In block 542, themachine readable instructions, when executed, may cause the OFScontroller 402 to adjust one or more fluid profiles stored in the memorymodules 420 or the wavelength and intensity information for thefluoresced visible light 396 received from the detector 312 based on theone or more temperature signals. The one or more temperature signals maybe from block 526 or block 540. To adjust the fluid profiles fortemperature, the processor 410 may query the memory modules 420 toretrieve one or more of the fluid profiles, which are stored in thememory modules 420. In one or more embodiments, the OFS controller 402may adjust both the fluid profiles and the wavelength and intensityinformation received from the detector 312 for changes in temperature.

In block 544, the machine readable instructions, when executed, maycause the OFS controller 402 to compare the wavelength and intensityinformation for the fluoresced visible light 396 received from thedetector 312 to the one or more fluid profiles stored in the one or morememory modules 420 to determine a fluid type of the fluid in the chamber306. Each of the one or more fluid profiles may comprise information onone or more fluorescent properties of the fluid (e.g., fluorescenceprofiles). The machine readable instructions, when executed, may causethe OFS controller 402 to query the memory modules 420 to retrieve theone or more fluid profiles. The OFS controller 402 may compare thewavelength and intensity of the fluoresced visible light 396 to the oneor more fluid profiles retrieved from the memory modules 420. The OFScontroller 402 may determine a fluid type of the fluid in the chamber306 based on the comparison of the wavelength and intensity of thefluoresced visible light 396 to the one or more fluid profiles. In block546, the machine readable instructions, when executed, may cause the OFScontroller 402 to determine whether a fluid type is successfullyidentified by the OFS controller 402. Referring to block 534, if the OFScontroller 402 determines that is has successfully identified a fluidtype of the fluid, the machine readable instructions, when executed, maycause the OFS controller 402 to generate and transmit a liquid type,which is indicative of the fluid type of the fluid in the chamber 306,to the system controller 70 and/or the OFS display 424. In one or moreembodiments, the OFS 130 may be positioned in contact with a tankcompartment 25 (FIG. 9) or control valve 45 (FIG. 9) of a producttransport vehicle 15 (FIG. 9) such that the liquid type may be atransported liquid type. In one or more embodiments, the OFS controller402 may generate an output signal indicative of a fluid type of thefluid in the chamber 306, and the system controller 70 may use theoutput from the OFS controller 402 to determine a transported liquidtype. Referring to block 548, if the OFS controller 402 has notdetermined the fluid type of the fluid in the chamber 306, then the OFScontroller 402 may generate an “unknown fluid type” message and transmitthe “unknown fluid type” message to the system controller 70.

Although FIG. 8 depicts method 520 as emitting visible light into thechamber 306 first and then emitting UV light second, in one or moreembodiments, the machine readable instructions, when executed, may causethe OFS controller 402 to emit UV light into the chamber 306 first andcompare the wavelength and intensity of fluoresced visible light 396received by the detector 312 to the fluid profiles before emittingvisible light into the chamber 306 and measuring the wavelength andintensity of visible light transmitted through the fluid in the chamber306. In one or more embodiments, the OFS controller 402 may operate todetermine whether a fluid is in the chamber 306, to determine a fluidtype of the fluid in the chamber 306, or both in response to receiving acontrol signal from the system controller 70. In one or moreembodiments, the OFS controller 402 may determine whether fluid ispresent in the chamber 306, according to method 500, at periodic timeintervals. In one or more embodiments, the OFS controller 402 maydetermine that a fluid is present in the chamber 306 before executingthe machine readable instructions to determine a fluid type of the fluidin the chamber 306.

In one or more embodiments, the machine readable instructions stored onthe one or more memory modules 420 may cause the OFS 130 to perform atleast the following when executed by processor 410: transmit a controlsignal to the light source 310 to cause the light source 310 to emitvisible light into the chamber 306; receive visible light at thedetector 312; process the received light to determine wavelength andintensity information for the received light; compare the wavelength andintensity information for the received visible light to one or morefluid profiles stored in the one or more memory modules 420; anddetermine a fluid type of the fluid in the chamber 306 based on thecomparison of the wavelength and intensity information for the receivedvisible light to the one or more fluid profiles.

In one or more embodiments, the machine readable instructions stored onthe one or more memory modules 420 may cause the OFS 130 to perform atleast the following when executed by processor 410: transmit a controlsignal to the light source 310 to cause the light source 310 to emit UVlight into the chamber 306 in order to cause the fluid to fluorescevisible light; receive visible light at the detector 312; process thereceived light to determine wavelength and intensity information for thereceived light; compare the wavelength and intensity information for thereceived light to one or more fluid profiles stored in the one or morememory modules 420, wherein each of the one or more fluid profilescomprises information on one or more fluorescent properties of thefluid; and determine a fluid type of the fluid in the chamber 360 basedon the comparison of the wavelength and intensity information for thereceived light to the one or more fluid profiles.

As previously discussed, the OFS 130 may be incorporated into acrossover protection system for preventing co-mingling of dissimilarliquid products during material transfer operations. Referring to FIG.9, a crossover protection system may include a product transport vehiclecomprising a tank compartment for containing a liquid product and avalve coupled to the tank compartment, the valve regulating a flow ofliquid product from the tank compartment. The valve may have a normallylocked state. The crossover protection system may have an OFS asdisclosed hereinabove positioned to contact the liquid product stored inthe tank compartment. The crossover protection system may also include atank delivery connector fluidly coupled to a distribution side of thevalve. The tank delivery connector may comprise a tank tag reader forinterrogating a tank tag coupled to a distribution tank separate fromthe product transport vehicle to retrieve a stored liquid type encodedon the tank tag. The stored liquid type is indicative of a fluid type ofthe liquid product (fluid) in the distribution tank. The crossoverprotection system may further comprise a system controllercommunicatively coupled to the valve, the optical fluid sensor, and thetank delivery connector. The system controller may comprise a processorand one or more memory modules communicatively coupled to the processor.The crossover protection system may further include machine readableinstructions stored in the one or more memory modules that cause thesensor to perform at least the following when executed by the processor:receive a transported liquid type from the optical fluid sensor; receivethe stored liquid type signal transmitted by the tank deliveryconnector; determine the stored liquid type based on the stored liquidtype signal; compare the transported liquid type to the stored liquidtype; maintain the valve in the normally locked state when the storedliquid type and the transported liquid type do not match to prevent theflow of liquid product from the tank compartment; and transition thevalve from the normally locked state to an unlocked state when thestored liquid type and the transported liquid type match, therebypermitting the flow of liquid product from the tank compartment.

Referring to FIG. 9, a product transport vehicle 15 at a distributionstation 20 is schematically depicted. The product transport vehicle 15may be used to transport liquid product between two points, such asbetween a fuel depot and retail distribution station 20. For example,the product transport vehicle 15 may be a tanker truck used to transportfuel products between the fuel depot (shown in FIG. 12) and thedistribution station 20. The product transport vehicle 15 may have aplurality of tank compartments 25 for containing liquid product, whereeach tank compartment 25 may have a manlid 30 and a hose adaptorassembly 35. Each hose adaptor assembly 35 may include an emergencyvalve 40 fluidly coupled to the bottom of the tank compartment 25, acontrol valve 45, and a pipe connection 50 fluidly coupling theemergency valve 40 to the control valve 45. An example of a suitableemergency valve 40 is the MaxAir series of internal valves by Civacon.An example of a suitable control valve 45 is the API Adaptor, modelnumber 891BA-LK by Civacon. However, it should be understood thatalternative valves may be used. A hose adaptor 133 may be coupled to thecontrol valve 45 or the pipe connection 50. In some embodiments, thecontrol valve 45 and the hose adaptor 133 are a single assembly as shownin FIGS. 15 and 16 and described in greater detail herein. An example ofa suitable hose adaptor 133 is the gravity coupler, model number 871 or876 by Civacon. However, it should be understood that alternative hoseadaptors may be used. In embodiments, the hose adaptor assembly 35 mayinclude both the emergency valve 40 and the control valve 45 as shown inFIG. 9. Alternatively, the hose adaptor assembly 35 may only includeeither the emergency valve 40 or the control valve 45. The individualvalves (control valve 45 and/or emergency valve 40) of the plurality ofvalves regulate the flow of liquid product into and out of thecorresponding tank compartment 25. A delivery hose 55 may be used tofluidly couple the hose adaptor 133 to a tank delivery connector 60. Thetank delivery connector 60, in turn, may be used to fluidly couple thetank compartment 25 with a distribution tank 65 located at thedistribution station 20. The tank delivery connector 60 may be removablycoupled to the delivery hose 55 and the distribution tank 65.

In the embodiments described herein, at least one of the control valve45 and the emergency valve 40 has a normally locked state. The phrase“normally locked state” means that the system controller 70 (describedin further detail herein) coupled to the valve (e.g. the emergency valve40 and/or the control valve 45) maintains the valve in a closed andlocked position and that the valve can only be unlocked uponconfirmation of a match between a stored liquid type and a transportedliquid type contained in a corresponding tank compartment 25. When amatch is confirmed, the system controller 70 transitions the valvecorresponding to a tank compartment 25 with the same product to anunlocked state. In the unlocked state, the valve can be opened or closedby an operator either manually or through the system controller, therebyfacilitating the unloading of the transported liquid product containedin the corresponding tank compartment 25.

Referring now to FIGS. 9-11, the crossover protection system 10 mayfurther include a system controller 70 and a tank tag reader 95 forinterrogating a tank tag 110 coupled to a distribution tank 65, such asan underground storage tank or similar storage tank. The crossoverprotection system 10 may include the OFS 130, a pressure sensor 135, acontroller antenna 75, an accelerometer 78 for determining when theproduct transport vehicle is in motion or stationary, a wirelesscommunication module 74, one or more input devices (not shown) such as akeypad or the like, a solenoid valve assembly to pneumatically controlthe plurality of valves (described in greater detail herein), a display80, a computer-readable medium (such as a memory or the like), and aprocessor. In some embodiments, the crossover protection system 10 mayfurther comprise a parking brake sensor 79 communicatively coupled tothe processor. The parking brake sensor 79 may be utilized to determinewhen the product transport vehicle 15 is parked such that a loading orunloading operation may be initiated.

The system controller 70 may be communicatively coupled to the OFS 130and the pressure sensor 135. An example of a suitable pressure sensor isthe diaphragm pressure sensor, model number 1E/F by Televac. However, itshould be understood that alternative pressure sensors may be used, suchas, for example, a piezo pressure sensor or an electric pressure sensor.It is contemplated that the OFS 130 and the pressure sensor 135, if bothare installed on the product transport vehicle 15, may be installed inthe same location or at separate locations. For example both the OFS 130and the pressure sensor 135 may be coupled to the tank compartment 25.Alternatively, the OFS 130 and/or the pressure sensor 135 may be coupledto the pipe connection 50. The OFS 130 may be positioned in the pipeconnection 50 such that the OFS 130 is able to interact with liquidproduct flowing through the pipe connection 50, thereby allowing thesystem controller 70 to discriminate between different liquid products,such as between different octane-grades of gasoline, dyed diesel types,organic solvents, aqueous solutions, resins, and other liquid products.

The crossover protection system 10 may also include one or more fluidproperty sensors (not shown) in addition to the OFS 130. An example of asuitable fluid property sensor may be the tuning fork sensor modelnumber FPS2800B12C4 by Measurement Specialties. However, it should beunderstood that alternative sensors may be used. In one or moreembodiments, the fluid property sensor may be located in the tankcompartment 25 and positioned to contact liquid product stored in thetank compartment.

The processor of the system controller 70 may be used to execute a setof instructions recorded on the computer-readable medium to prevent thecross contamination of product stored in the distribution tank 65 withdissimilar product stored in one or more of the tank compartments 25 ofthe product transport vehicle 15. The processor may be communicativelycoupled to the controller antenna 75, accelerometer 78, wirelesscommunication module 74, one or more input devices, the display 80, andthe computer-readable medium. The system controller 70 may be powered by12 volt direct current (VDC) or 24 VDC power or a portable power sourcesuch as a battery source and/or a solar cell, for example. The display80 may be an alphanumeric display that presents information, such assystem status or the like, to the operator. The display 80 may bepositioned anywhere on the product transport vehicle 15 and may beelectrically coupled to the system controller 70. For example, in oneembodiment, the display 80 is wirelessly coupled to the systemcontroller 70 and is positionable and relocatable on the producttransport vehicle 15. In embodiments, status information displayed onthe display 80 may include which tank compartments 25 are empty or havesome amount of liquid product in them as indicated by the plurality ofpressure sensors 135. In embodiments, status information may alsoinclude the transported liquid type associated with each tankcompartment 25 as sensed and determined by an OFS 130, whichcommunicates the transported liquid type to the system controller 70.Further, status information may also include the stored liquid type ofthe liquid product stored in a distribution tank 65. In addition to thetransported liquid type of the liquid product in each tank compartment25, other information related to the crossover protection system 10 mayalso be presented, including, without limitation, battery liferemaining, any fault codes, and/or tank tag identification information.The display 80 may include a schematic diagram of the product transportvehicle 15 indicating the status of the tank compartments 25 andschematically depicting fluid flow while in operation. In embodiments,the display 80 may be a touch screen. The keypad or plurality of inputdevices may include north, south, east, west arrow navigation keys, anenter key, an override key, and/or a numeric keypad.

The system controller 70 may include a set of communication ports (notshown) to communicatively connect to the wireless communication module74, or to an in-cab black box (not shown) where the processor,computer-readable medium, an onboard overfill detection system (notshown), and other components that may reside on the product transportvehicle 15. A local power port (not shown) may be included to providepower to the system controller 70 in the event the power source failureor battery source failure/depletion. The system controller 70 may beconnected to other devices, such as the OFS 130, for example, by wired,wireless, and/or optical communications. A communication port may beincluded to communicatively connect to other devices using RS-485protocol, CANbus protocol J1939, CAN open, or a similar protocol, and a6-pin cable. The tank tag reader 95 may be communicatively coupled tothe system controller 70 with electrical wires (not shown) or wirelesslyutilizing standard wireless communication protocols. Suitable wirelesscommunication protocols may include the 802.11 families of protocols,the Bluetooth® protocol, the ZigBee IEEE 802 Standard protocol, or thelike. In some embodiments, the system controller 70 may wirelesslycommunicate with the tank tag reader 95 via a pair of antennas, forexample the controller antenna 75 and/or the tank connector antenna 115.Additionally, the system controller 70 may also be communicativelycoupled to a LAN or WAN through one or more Ethernet cables or wirelessEthernet connections.

The system controller 70 may log and time stamp all events as they occurwithin the crossover protection system 10. For example, the systemcontroller 70 may log trip records, stored liquid type, transportedliquid type, tank compartment usage, amount of liquid product loaded andunloaded, and similar events. The system controller log may bedownloaded and used to reconstruct trip events with a computer. Inembodiments, the computer-readable medium (i.e., memory) may be largeenough to hold either an estimated 30 days worth of trip logs.Alternatively or additionally, the computer-readable medium may be largeenough to hold an estimated 200 trip logs. In some embodiments, thein-cab black box may be communicatively connected to an on-truckcomputer (not shown) to enable the logs to be uploaded to a remotecomputer system wirelessly through the on-product transport vehiclecommunication systems.

Referring specifically to FIG. 10, the crossover protection system 10 isschematically depicted as it relates to components on the producttransport vehicle 15 of FIG. 9. The system controller 70 may receive atransported fluid type from the OFS 130. The system controller 70 mayoptionally receive a fluid property signal from an optional fluidproperty sensor supplemental to the OFS 130, the fluid property signalindicative of at least one of a viscosity of the liquid product in thetank compartment 25, a density of the liquid product in the tankcompartment 25, a dielectric constant of the liquid product in the tankcompartment 25, and a temperature of the liquid product in the tankcompartment 25. In some embodiments, the system controller 70 mayinclude a liquid type LUT stored in memory. The LUT may contain aplurality of liquid types indexed according to one or more fluidproperties at a specified temperature or temperatures. These propertiesmay include the viscosity, density, dielectric constant, or combinationsthereof. Using this LUT, the system controller 70 may verify thetransported liquid type received from the OFS 130 by comparing thetransported liquid type from the OFS 130 against a liquid type indicatedby the fluid property signal received from the fluid property sensor.

As noted hereinabove, the pressure sensor 135 may be positioned ineither the pipe connection 50 or the tank compartment 25 such that thepressure sensor 135 is able to detect the pressure of the liquid productwithin the pipe connection 50 and the tank compartment 25, therebyallowing the system controller 70 to detect static pressure in the tankcompartment 25 and gauge the approximate level or amount of product inthe tank compartment 25. The PGI controller 125 may also display theamount of liquid product remaining in the tank compartment 25 asdetermined by the pressure sensor 135. In another embodiment, the systemcontroller 70 may display the amount of liquid product remaining in thetank compartment 25 as determined by the pressure sensor 135 on thedisplay 80. The system controller 70 may receive a pressure signal fromthe pressure sensor 135. The pressure signal may indicate the amount ofliquid product present in the tank compartment 25. The system controller70 may display the transported liquid type obtained from the OFS 130and/or the amount of liquid product indicated by the pressure signal onthe display 80 of FIG. 9.

The system controller 70 may also receive an accelerometer signal fromthe accelerometer 78. The accelerometer signal may indicate whether theproduct transport vehicle 15 is in motion or not. The system controller70 may use the accelerometer signal to either maintain the valves in thenormally locked state while the product transport vehicle 15 is inmotion or transition the valves to the normally locked state when theaccelerometer 78 indicates that the product transport vehicle 15 hasstarted to move.

Still referring to FIG. 10, in some embodiments, one or more PGIcontrollers 125 may be communicatively coupled with the plurality of OFS130 and the plurality of pressure sensors 135. In embodiments,individual PGI controllers 125 may be associated with a specific hoseadaptor assembly 35 and/or associated tank compartment 25 and may beused in conjunction with the system controller to regulate the flow offluid to and from each tank compartment. However, it should beunderstood that the PGI controllers are optional and that in someembodiments the crossover protection system 10 does not utilize PGIcontrollers.

Referring now to FIG. 11A, an embodiment of a PGI controller 125 isschematically depicted. Each PGI controller 125 of the plurality of PGIcontrollers is associated with a tank compartment 25 of the plurality oftank compartments. The PGI controller 125 may have a computer-readablemedium (i.e., a memory) and a processor to execute a set of instructionsrecorded on the computer-readable medium. The processor may becommunicatively coupled to a PGI display 140, a plurality of inputdevices 145, an alert device, a solenoid valve assembly to pneumaticallycontrol the valves corresponding to the tank compartment 25 the PGIcontroller 125 is associated with, a pressure switch 155, a loading armsensor (loading arm proximity/detection sensor) input and thecomputer-readable medium. The PGI display 140, such as a liquid crystaldisplay or a similar electronic display, is mounted to a PGI face 142 ofthe PGI controller 125. The plurality of input devices 145 may also bemounted to the PGI face 142 of the PGI controller 125 to allow anoperator to interact with the PGI controller 125 and enter liquidproduct identification information into the PGI controller 125. Theplurality of input devices 145 and the PGI display 140 allow an operatorto choose the liquid product type that is being loaded into the tankcompartment 25 to which the PGI controller 125 is associated. Forexample, the plurality of input devices 145 may be buttons to allow theoperator to scroll up and down through a list of liquid product typesstored in a computer readable medium of the PGI controller 125 anddisplayed on the PGI display 140. The input devices 145 allow theoperator to make a selection from the list or, alternatively, todirectly input liquid product information into the PGI controller 125identifying the contents of the tank compartment 25 of the producttransport vehicle 15. In some embodiments, the PGI controller 125 mayinclude an “empty” input device which allows the operator to quicklyindicate the tank compartment 25 is empty. The plurality of inputdevices 145 may include, without limitation, a keypad, scroll wheel,touchpad, or any other suitable input device that enables an operator tointeract with the PGI controller 125. In some embodiments, an audiodevice 160 may be mounted to the face of the PGI controller 125 and mayprovide an audible signal to draw the attention of the operator to thePGI controller 125.

A PGI connector 165 may be connected to a PGI body 144 to electricallycouple the plurality of PGI controllers 125 together and to electricallycouple the plurality of PGI controllers 125 to the system controller 70.A sensor connector 167 may be connected to the PGI body 144 toelectrically couple the pressure sensor 135 to the PGI controller 125and/or communicatively couple the OFS 130 to the PGI controller 125. Anair input connector 170 and an air output connector 175 for use by a PGIpneumatic system 180 as shown in FIG. 11B may also be mounted to the PGIbody 144.

Referring now to FIGS. 10, 11A, and 11B, FIG. 11B is a schematic view ofthe PGI pneumatic system 180. The PGI pneumatic system 180 may becoupled to the hose adaptor assembly 35 (FIG. 9), the emergency valve 40and/or the control valve 45 (FIG. 9). FIG. 11B depicts the PGIcontroller coupled to the emergency valve 40. The PGI pneumatic system180 either maintains the valve to which it is connected in the normallylocked state and transitions the valve from the normally locked state toan unlocked state based on instructions received from the PGI controller125 (FIG. 11A) and/or the system controller 70 (FIG. 10). The solenoidvalve assembly 150 and the pressure switch 155 of the PGI pneumaticsystem may be mounted internal to the PGI controller 125 or the systemcontroller 70 (FIG. 10). Referring to FIGS. 11A and 11B, pressurized airmay be fed into the solenoid valve assembly 150 through the air inputconnector 170 on the PGI body 144 or a system controller body (notshown). When the PGI controller 125 or system controller 70 (FIG. 10)opens the solenoid valve assembly 150, the pressurized air actuates thepressure switch 155 and transitions the valve from the normally lockedstate to the unlocked state thereby allowing liquid product to flow outof the tank compartment 25 (FIG. 9). The PGI pneumatic system 180delivers pressurized air to the valve using the air output connector175. In embodiments, the solenoid valve assembly 150 may be manuallyopened by the operator activating a valve manual override input deviceon the PGI controller 125 or the system controller 70. In someembodiments, the solenoid valve assembly 150 may be a normally lockedsolenoid valve. Based on the foregoing, it should be understood that thePGI pneumatic system 180, whether contained in the PGI controller 125 orthe system controller 70 (FIG. 10), may control the locking/unlocking ofthe corresponding valve as well as the opening and closing of thecorresponding valve to allow or prevent fluid flow.

While the PGI pneumatic system has been described herein as beingcoupled to or a part of the PGI controller, in some embodiments, thesystem controller 70 (FIG. 10) may incorporate all the functions of theplurality of PGI controllers 125. In these embodiments, the systemcontroller 70 includes the PGI pneumatic system 180 for each valve onthe product transport vehicle 15. For example, all the solenoid valveassemblies 150 may be combined together in a manifold arrangement andmounted in a separate location and electrically coupled to the systemcontroller 70. In these embodiments, the system controller 70 may alsoinclude the plurality of input devices 145, and alert devices. Thiswould eliminate the need for a plurality of PGI controllers 125 andassociated equipment.

Referring to FIG. 10, in embodiments, the PGI controller 125 may be usedby an operator to manually enter the transported liquid type into thesystem controller 70. The transported liquid type from the OFS 130and/or the pressure signal from the pressure sensor 135 may also bereceived by an individual PGI controller 125. The PGI controller 125 maybe communicatively coupled with the system controller 70 and maytransmit the transported liquid type and/or the pressure signal to thesystem controller 70 for processing by the processor. The transportedfluid property type signal from the optional fluid property sensor mayalso be received by an individual PGI controller 125 and transmitted onto the system controller 70. The PGI controller 125 may also display thetransported liquid type received from the OFS 130 and/or the amount ofliquid product indicated by the pressure signal on the PGI display 140(FIG. 11A).

The operator may override the system controller 70 using the pluralityof input devices 145 on the PGI controller 125 or on the systemcontroller 70. A log of any override action taken by the operator may bestored in the system controller 70 memory for later retrieval andanalysis.

In some embodiments, each PGI controller 125 may be communicativelycoupled to another PGI controller 125 as shown in FIG. 10 or multiplePGI controllers 125, and at least one of the PGI controllers 125 iscoupled to the system controller 70. Alternatively, each PGI controller125 may be directly coupled to the system controller 70. In oneembodiment, a total of twelve PGI controllers 125 may be communicativelycoupled to the system controller 70 with a six-pin cable 137, such aswhen the product transport vehicle 15 (shown in FIG. 9) contains twelveseparate tank compartments 25. In some embodiments, a PGI controller 125may be mounted to each hose adaptor assembly 35 and may be used toindicate the transported liquid type of the liquid product that isstored in the tank compartment 25. For example, the PGI controller 125receives the transported liquid type of the liquid product stored in thetank compartment 25 from either the system controller 70 or the OFS 130and displays the liquid product type. The display of information may bedone on the display 80 and/or a PGI display 140 (shown in FIG. 11A). Inanother embodiment, an operator may input a loaded liquid type of liquidproduct that is being stored in the tank compartment 25 directly intothe PGI controller 125 when the tank compartment 25 is filled at theloading station. The PGI controller 125 may display the loaded liquidtype. The display of information may be done on the display 80 and/or aPGI display 140 (shown in FIG. 11A). In embodiments where the producttransport vehicle 15 is used to store liquid petroleum products, thetype of liquid product may be, for example gasoline, diesel, kerosene,etc. However, it should be understood that other types of liquidproducts may be stored in the tank compartments 25 and the PGIcontroller 125 and/or the system controller 70 may be used in a similarmanner to identify those liquid products.

Referring again to FIG. 9, in embodiments, the hose adaptor assembly 35for each tank compartment 25 may be fluidly coupled to a distributiontank 65 with a tank delivery connector 60 and a delivery hose 55. Thetank delivery connector 60 may be an elbow coupler, a straight coupler,or a flexible coupler. An example of a suitable tank delivery connector60 is the product delivery elbow, model number 60TT, 65TT, or 70TT byCivacon. However, it should be understood that alternative tank deliveryconnectors may be used. In embodiments where a tank delivery connector60 is used to fluidly couple the hose adaptor assembly 35 to adistribution tank 65, the tank tag reader 95 may be located on the tankdelivery connector 60 and positioned to read a corresponding tank tag110 located on the distribution tank 65 when the tank delivery connector60 is coupled to the distribution tank 65.

While FIG. 9 schematically depicts the use of a tank delivery connector60 to couple the hose adaptor assembly 35 to the distribution tank 65,it should be understood that, in some embodiments, the tank deliveryconnector 60 may be omitted, such as when the hose adaptor assembly 35is directly coupled to a distribution tank 65 with a delivery hose. Inthese embodiments, the tank tag reader 95 may be located on one end ofthe delivery hose and positioned to read a corresponding tank tag 110located on the distribution tank 65 when the delivery hose is coupled tothe distribution tank 65.

In some embodiments, the system controller 70 and associated componentsmay be configured to determine that a valve corresponding to a tankcompartment 25 to be unloaded is fluidly connected to a correspondingtank delivery connector 60 attached to a distribution tank 65 to preventproduct spills. In some embodiments, the system controller 70 may alsoconfirm that the same delivery hose 55 is fluidly coupled between thevalve and the tank delivery connector 60 utilizing a set of RFID tagsand a plurality of tag readers.

The system controller 70 may be communicatively coupled to an adaptortag reader 85 and a hose tag reader 90. The adaptor tag reader 85 may bepositioned on the hose adaptor 133 or a valve, e.g. the control valve45. The hose tag reader 90 may be positioned on the tank deliveryconnector 60 in a location adjacent to the coupling point of a deliveryhose 55 and opposite the tank tag reader 95. The delivery hose 55 mayhave a lock tag 100 at a lock end 102 of the delivery hose 55 and aconnector hose tag 105 at a connector end 103 of the delivery hose 55.Both the lock tag 100 and the connector hose tag 105 may have the samehose ID information encoded on them, e.g. a first hose ID, a second hoseID, etc.

When the delivery hose 55 is coupled to the hose adaptor 133, theadaptor tag reader 85 interrogates the lock tag 100 and transmits theidentification information (e.g. the first hose ID) to the systemcontroller 70. When the delivery hose 55 is coupled to the tank deliveryconnector 60, the hose tag reader 90 interrogates the connector hose tag105 and transmits the identification information (e.g. the first hoseID) to the system controller 70.

Referring to FIGS. 15 and 16, a front view and a side view of thecontrol valve 45 is depicted. The control valve 45 and the hose adaptor133 may be a single assembly as shown. The adaptor tag reader 85 may becoupled to a tag mount 800 and positioned on the hose adaptor 133 asshown or on the control valve body 810. In some embodiments, the OFS 130may also be coupled to the control valve body 810 as shown. A controlvalve lever 815 is coupled to the control valve 45 and used by theoperator to manually (e.g. physically) transition the control valve 45from the normally locked state to the unlocked state. A pneumatic lock820 may be coupled to the control valve body 810 and pneumaticallycoupled to the solenoid valve assembly of the PGI controller and/or thesystem controller. The pneumatic lock 820, when enabled by the PGIcontroller and/or the system controller 70, allows the control valve 45to be transition from the normally locked state to the unlocked stateand thereby open the control valve 45. The pneumatic lock 820 is coupledto the control valve lever 815 internal to the control valve body 810and mechanically restricts (i.e. stops) the movement of the controlvalve 45 in the normally locked state.

In one embodiment, the system controller 70 verifies that a deliveryhose 55 is coupled to each of the tank delivery connector 60 and thehose adaptor 133 and/or control valve 45. For example, when the deliveryhose 55 is properly coupled to the tank delivery connector 60, the hosetag reader 90 is positioned to read the connector hose tag 105 andtransmit a hose signal indicative of the hose ID to the systemcontroller 70. In this embodiment, receipt of the hose signal indicativeof the hose ID by the system controller 70 is sufficient to confirm thatthe delivery hose 55 is properly coupled to the tank delivery connector60. Similarly, when the delivery hose 55 is properly coupled to the hoseadaptor 133 or the control valve 45, the adaptor tag reader 85 ispositioned to read the lock tag 100 and transmit a hose signalindicative of the hose ID to the system controller 70. In thisembodiment, receipt of the hose signal indicative of the hose ID by thesystem controller 70 is sufficient to confirm that the hose is properlycoupled to the hose adaptor 133 or the control valve 45. When the systemcontroller 70 confirms that the delivery hose 55 is properly coupled toboth the tank delivery connector 60 and the hose adaptor 133 or controlvalve 45, the system controller 70 may allow the corresponding controlvalve 45 to transition from the normally locked state to the unlockedstate, subject to a determination that the transported liquid producttype in the corresponding compartment matches the stored liquid producttype of the distribution tank 65.

In another embodiment, the system controller 70 may confirm that aspecific tank compartment 25 is fluidly coupled to a specificdistribution tank 65 by matching the identification information of thelock tag 100 and the connector hose tag 105 and verifying the deliveryhose 55 fluidly connects the specific control valve 45 or hose adaptor133 to the correct tank delivery connector 60.

For example, the adaptor tag reader 85 may transmit the hose IDinformation to the system controller 70 using a bus or similar wiringmethod. In another embodiment, the adaptor tag reader 85 may transmitthe hose ID information to the system controller 70 using a wirelessconnection, such as the wireless protocol and devices described herein.The hose tag reader 90 transmits the hose ID information to the systemcontroller 70 using a wireless connection, such as the wireless protocoland devices as described above.

The tank tag reader 95 may further transmit a tank delivery connector IDsignal to the system controller 70 indicative of an identity of the tankdelivery connector 60. The tank delivery connector ID signal may be usedto pair the tank delivery connector 60 to the system controller 70associated with the product transport vehicle 15. For example, referringto FIG. 13, the system controller 70 may be paired with a first tankdelivery connector 60 a having a first tank delivery connector ID and asecond tank delivery connector 60 b having a second tank delivery ID.The pairing of the first tank delivery connector 60 a and the secondtank delivery connector 60 b may ensure that the system controller 70 isnot processing any information relating to a non-paired tank deliveryconnector 60 at the same distribution station 20.

When the system controller confirms that the delivery hose 55 isproperly coupled to both the tank delivery connector 60 and the hoseadaptor 133 or control valve 45 based on the received hose IDinformation, the system controller 70 may allow the correspondingcontrol valve 45 to transition from the normally locked state to theunlocked state, subject to a determination that the transported liquidtype of the liquid product in the corresponding tank compartment 25matches the stored liquid product type of the distribution tank 65.

In another embodiment, the crossover protection system 10 configurationmay be such that the delivery hose 55 may not have a lock tag 100attached to the lock end 102 or connector hose tag 105 attached to theconnector end 103 of the delivery hose 55 as described above. The tanktag reader 95 may read the tank tag 110 and transmit the tank tag'sencoded liquid product type information directly to the systemcontroller 70. The system controller 70 may allow or not allow theliquid product transfer based on the liquid product type informationfrom the tank tag 110 without the need to verify the identity of thedelivery hose 55. In this embodiment, the system controller 70 mayenable only those valves that correspond to those tank compartments 25that have a matching transported liquid type to transition from thenormally locked state to the unlocked state. The system controller 70may not act upon, or receive any other stored liquid type signals fromother tank tag readers until one of the valves that has been enabled istransitioned to the unlocked state. The system controller 70, by onlyallowing a single tank compartment 25 to be unloaded at a time, candetermine that the tank delivery connector 60 attached to thedistribution tank 65 and is fluidly coupled to the matching tankcompartment 25.

Referring now to FIGS. 9, 13, and 14, in another embodiment, the tankdelivery connector 60 may include a lock mechanism 700 coupled to thetank delivery connector 60, a power supply (not shown), and a locksensor 705. The lock mechanism 700 may include a locking lever 710 witha locked position and an unlocked position coupled to a locking clamp720. The locking lever 710, when in the unlocked position, maneuvers thelocking clamp 720, via a lock shaft 725, to allow the coupling of thetank delivery connector 60 to the distribution tank 65. In the lockedposition, the locking lever 710 maneuvers the locking clamp 720, via thelock shaft 725, to compress a coupler (not shown) on the distributiontank to the tank delivery connector 60. In the locked position, the lockmechanism 700 mechanically secures the tank delivery connector 60 to acorresponding distribution tank 65. The power supply is coupled to thetank delivery connector and provides power for the tank tag reader 95;the hose tag reader 90 and/or the lock sensor 705. The lock sensor 705is mechanically coupled to the lock mechanism 700 and electricallycoupled to the tank tag reader 95 and may be a magnetic sensor, contactsensor, optical sensor, or the like. In one embodiment, the lock sensor705 is a proximity sensor which senses whether the locking lever 710 isin the locked position and/or the unlocked position based on the lockinglever's 710 position relative to the lock sensor 705. For example, thelock sensor 705 may provide the tank tag reader 95 with a deliveryconnector locked signal when the locking lever 710 is in the lockedposition. The tank tag reader 95 transmits the delivery connector lockedsignal to the system controller 70 when the tank delivery connector 60is secured to the distribution tank 65. In one embodiment, power to thetank tag reader 95 may only be provided when the locking lever 710 is inthe locked position as indicated by the lock sensor 705. The systemcontroller 70 will not receive the tank tag signal until the tankdelivery connector 60 is coupled to the distribution tank 65 and thelocking lever 710 is in the locked position.

In yet another embodiment, the tank delivery connector 60 may includethe lock mechanism 700 for locking the tank delivery connector 60 to thedistribution tank 65, the power supply, and a switch (not shown). Theswitch may be mechanically coupled to the lock mechanism 700 andelectrically coupled to the power supply and the tank tag reader 95.When the switch is actuated (e.g. pressed or toggled), the tank tagreader 95 will interrogate the tank tag 110 and transmit the storedliquid type signal to the system controller 70. In some embodiments, theswitch may be positioned such that transitioning the locking lever 710of the lock mechanism 700 from the unlocked state to the locked statemay toggle the switch. In these embodiments, the switch may be used to“wake-up” the tank tag reader 95 which then automatically reads the tanktag 110 and transmits the stored fluid type signal to the systemcontroller 70.

As described herein, the system controller 70 may use tags to preventthe mixing of dissimilar liquid products during loading and unloading ofthe liquid product and to verify coupling between the tank compartmentsof the product transport vehicle and a distribution tank. The adaptortag reader 85, hose tag reader 90, and tank tag reader 95 (tag readers)shown in FIG. 9 may interrogate the lock tag 100, connector hose tag105, and the tank tag 110 (tags) during operation of the crossoverprotection system 10. These tag readers may use optical interrogation,radio frequency interrogation, and/or physical interrogation to read theinformation encoded on the tags. For example, the tag readers may use anoptical device, such as an image sensor, to take an image of the tag anddecode the information contained on the tag. The tag reader may also bea laser scanner and/or bar code reader used to read the tag which mayinclude a barcode or equivalent indicia. Alternatively, the tag readersinclude tactile input devices such as keypads or the like such that aproduct ID number found on the tag may be input into the tag reader byan operator. In the embodiments described herein, the tag readers areRadio Frequency Identification Device (RFID) tag reader and the tags areRFID tags. In embodiments, the tags may be passive RFID tags where thetag does not allow a read/write capability to occur within a tag memory.

In yet another embodiment, the system configuration may be such that thetags may be active RFID tags. The active RFID tag may allow the tagreaders to read the tag's encoded information and write or overwriteinformation on the tags. For example, the liquid product typeinformation may need to be changed to correspond to a change in type ofliquid product being stored in the distribution tank 65. Or additionalinformation may need to be included to the encoded information such as,for example, a timestamp of the last fill, the delivery vehicle IDnumber, the delivery company name, and/or batch number of the liquidproduct, etc.

Referring to FIG. 12, in some embodiments, the system controller 70 mayfurther include a loading arm sensor 250. The loading arm sensor 250 maybe mounted on the hose adaptor assembly 35 or the hose adaptor 133 andprovides a loading arm signal to the PGI controller 125 and/or systemcontroller 70 to determine when the loading arm 200, is fluidly coupledto the hose adaptor assembly 35 or hose adaptor 133. If the loading armsensor 250 indicates that the loading arm 200 is not coupled to an hoseadaptor assembly 35, the PGI controller 125 indicates on the PGI display140 and/or the display 80 that the delivery hose 55 is not coupled toany of the storage compartments of the product transport vehicle 15 andthe system controller 70 maintains the valve in the normally lockedstate to prevent a spill.

The operation of the crossover protection system 10 during loading andunloading of the product transport vehicle will now be described in moredetail with specific reference to the Figures.

Referring now to FIG. 12, a product transport vehicle 15 isschematically depicted at a loading station. In some embodiments, theproduct transport vehicle 15 may arrive at the loading stationcompletely empty. In the “empty” state, the PGI controller 125 and/orthe system controller 70 may have the loaded liquid type in a particulartank compartment set either by the operator using the plurality of inputdevices 145 or by the OFS 130, which may indicate that a fluid is notpresent in chamber 306 (FIG. 2) of the sensor housing 304 (FIG. 2)indicating no liquid product in the tank compartment 25 or transferpipe, or the pressure sensor 135 indicating the amount of liquid productis zero or near zero. In the later cases, the loaded liquid type may beset to “empty” when there is no liquid product in a particular tankcompartment In some other embodiments, the product transport vehicle 15may arrive at the loading station with at least one of the plurality oftank compartments 25 empty, as for example if the product transportvehicle 15 just returned from a product delivery run. The PGI controller125 associated with that tank compartment 25 will indicate the laststatus from the product delivery run. For example, if the tankcompartment 25 is empty, the PGI display 140 may indicate “empty”automatically based on readings from either the pressure sensor 135 orthe OFS 130 and without input from the operator. Otherwise, the PGIdisplay 140 will display an error code alternating message between“Prior Product Grade”, “Retained Product”, and “Frustrated Load” toindicate the tank compartment 25 is not empty from the product deliveryrun. The error code messages are related and may only scroll due to thelimitations of the PGI display 140. The “Prior Product Grade” messageindicates what product was in the tank compartment 25. The “RetainedProduct” message indicates that there is product left in the tankcompartment 25, and the “Frustrated Load” message indicates that not allof the product was delivered to the distribution tank 65. To alert theoperator to make a selection before filling the tank compartments 25, analerting device associated with the PGI controller may be used. Examplesof suitable alerting devices include, without limitation, an audiblealert produced by an audio device 160, a flashing message or color fromthe PGI display 140, and/or a visual device, such as one or more LEDs(not shown). The alerting device may be associated with a specific PGIcontroller 125 allowing the operator to easily locate which PGIcontroller 125 needs attention. If the PGI controller 125 is not used onthe product transport vehicle 15, the system controller 70 may indicatethe status of individual tank compartments 25 of the plurality of tankcompartments using the above convention, the display 80, and an alertingdevice associated with the system controller 70.

Referring to FIGS. 10, 11A, 11B, and 12, to load liquid product into thetank compartment 25, a loading arm 200 is connected to the hose adaptor133 of the hose adaptor assembly 35 to fill the corresponding tankcompartment 25. The loading arm 200 is fluidly coupled to a storage tank(not shown) of the loading station. In one embodiment, the PGIcontroller 125 may not allow the operator to load the liquid productinto one or more of the tank compartments 25 until the loaded liquidtype is selected as discussed above. The PGI controller 125 may receivea valve open air signal from an air selector valve panel (not shown)indicating the operator has tried to open an individual valve of theplurality of valves. The PGI controller 125 and/or the system controller70 may display an error message and instruct the operator that theloaded liquid type is not selected or that a mismatch of liquid typesmay occur between the liquid product the operator wishes to load and acurrent transported liquid type already present in the tank compartment25. The PGI controller 125 and/or system controller may maintain thecorresponding valve in the normally locked state until the PGIcontroller 125 and/or the system controller 70 indicate that the loadedliquid type has been entered and/or the loaded liquid type and thetransported liquid type are the same. Once the loaded liquid type isaccepted by the PGI controller 125 and/or system controller 70, the PGIcontroller and/or system controller 70 may enable the correspondingvalve to transition from the normally locked state to the unlocked stateand the operator may then manually transition the valve to open and fillthe tank compartment 25 with the liquid product.

In embodiments, the PGI controller 125 and/or the system controller 70may be communicatively coupled to the braking system of the producttransport vehicle 15, either pneumatically or electrically, as describedabove. In these embodiments, the system controller 70 may require abrake signal to indicate that the parking brake on the product transportvehicle 15 is released before loading or unloading of the liquid productmay be allowed to proceed. The PGI controller 125 and/or the systemcontroller 70 may be coupled to the parking brake sensor 79 whichprovides the brake signal. The brake signal is indicative of whether thebrake is engaged or released. In other embodiments, the systemcontroller 70 may use multiple indicators to determine the producttransport vehicle's current mode of operation (i.e. loading or unloadingproduct). These indicators may include, for example, the brake signal,the pressure sensor signals, and communications with the OFS 130. In asimilar manner, the system controller 70 may utilize the accelerometersignal from the accelerometer 78 to determine if the product transportvehicle 15 is moving before allowing any of the plurality of valves totransition from the normally locked state to the unlocked state andallow product loading/unloading to occur. For example, if theaccelerometer 78 indicates that the product transport vehicle is moving,the system controller 70 may prevent the emergency valve 40 and/or thecontrol valve 45 from being transitioned from the normally locked stateto the unlocked state. Likewise, once the accelerometer 78 indicatesthat the transport vehicle has begun moving, the PGI controller 125and/or the system controller 70 may transition the valve from theunlocked state to the normally locked state to cease any loading orunloading of product from or to the tank compartment 25 and indicatethat the current operating mode has concluded.

In one embodiment, as the tank compartment 25 is filled, the OFS 130determines the transported liquid type of the liquid product, asdescribed previously herein. The PGI controller 125 and/or the systemcontroller 70 may read or poll the OFS 130 to receive the transportedliquid type determined for the liquid product by the OFS 130. In one ormore embodiments, the identity of the liquid product is stored in thecomputer-readable medium of the PGI controller and/or the systemcontroller 70 and indexed according to the associated tank compartment25 such that the contents of each tank compartment are recorded in thecomputer-readable medium. In some other embodiments, the OFS 130 isutilized to continuously or periodically monitor and determine the fluidtype of the liquid stored in the tank compartment 25 and continuously orperiodically provide the system controller 70 with the transportedliquid type.

If, for example, the system controller 70 determines that thetransported liquid type from the OFS 130 does not match the loadedliquid type indicated by the operator through the PGI controller 125,the system controller 70 and/or the PGI controller 125 will eithermaintain the valve in the normally locked state or transition the valvefrom the unlocked state to the normally locked state, thereby closingthe valve and stopping the flow of liquid product into the tankcompartment 25. The operator may override the system controller 70 tomanually transition the valve from the normally locked state to theunlocked state and continue filling the tank compartment 25.

In another embodiment, the system controller 70 or the PGI controller125 may mimic an error indicator of an existing control system on theproduct transport vehicle 15 to stop the flow of liquid product into thetank compartment 25 when the system controller 70 determines that thetransported liquid type from the OFS 130 does not matches the loadedliquid type indicated by the operator. For example, the systemcontroller 70 or the PGI controller 125 may stop the flow of liquidproduct from the storage tank to the tank compartment 25 by mimicking anoverfill condition in the tank compartment to the onboard overfilldetection system (not shown). The overfill condition may be communicatedto the onboard overfill detection system coupled to the tank compartment25 via an overfill condition signal. The onboard overfill detectionsystem monitors for an overfill condition in the individual tankcompartments 25 of the product transport vehicle 15 using a point levelsensor (not shown). The point level sensor may be positioned in the tankcompartment and transmit a point signal to the system controller 70 toindicate whether there is an overfill condition of liquid product withinthe tank compartment 25.

The onboard overfill detection system on the product transport vehicle15 is communicatively coupled to a loading station control system (notshown) in the loading station. The loading station control systemcontrols the flow of liquid product from the storage tanks. When thesystem controller 70 or the PGI controller 125 determines that thetransported liquid type from the OFS 130 does not match the loadedliquid type indicated by the operator, the overfill condition signal maybe transmitted to the onboard overfill detection system. The onboardoverfill detection system will instruct the loading station controlsystem to cease loading liquid product onto the tank compartment 25 onthe product transport vehicle.

In another embodiment, the system controller 70 and/or PGI controller125 may receive a valve open signal indicating the operator has openedthe emergency valve 40 and/or the control valve 45 to allow the loadingof liquid product into the tank compartment 25. The PGI controller 125and/or the system controller 70 may then start to poll the OFS 130 todetermine the transported liquid type of the liquid product. Theidentity (i.e., transported liquid type) of the liquid product is storedin the computer-readable medium of the PGI controller and/or the systemcontroller 70 and indexed according to the associated tank compartment25 such that the contents of each tank are recorded in acomputer-readable medium.

Where the liquid product is a petroleum product, the PGI controller 125and/or system controller 70 determine whether the liquid product in thetank compartment 25 is a distillate or gasoline liquid product based onthe transported liquid type received from the OFS 130. When thetransported liquid type indicates that the liquid product is gasoline,the PGI controller 125 and/or system controller 70 may alert theoperator to enter in the product grade (i.e., the octane rating) of thegasoline that has been loaded into the tank compartment 25 by flashing“Set Grade” on the PGI display. In this embodiment, the operator mayselect from a variety of pre-programmed options to set the grade of theliquid product being loaded. The PGI controller 125 electricallycommunicates a signal encoding the selection to the system controller70. The system controller 70 stores, in a computer readable medium, theliquid product type information for the tank compartment 25 holding theliquid product. The system controller 70 may poll the OFS 130 to receivethe transported liquid type determined by OFS 130 continuously or atperiodic intervals during transfer of the material. The systemcontroller 70 may compare the transported liquid type received from theOFS 130 to the liquid product type and grade entered by the operator.The process is repeated as other tank compartments 25 are filled in theproduct transport vehicle 15 with either the same liquid product or adifferent liquid product.

Still referring to FIG. 12, in one embodiment, the loading arm 200 mayinclude a loading arm tag 205 having the loaded liquid type encodedtherein. The adaptor tag reader 85 may interrogate the loading arm tag205 and transmit a first signal encoding a loaded liquid type to thesystem controller 70. The loaded liquid type information is received bythe wireless module and recorded to a computer readable medium of thesystem controller 70. The loaded liquid type information is correlatedto the tank compartment 25 that the liquid product is being loaded into.As the liquid product is being loaded into the tank compartment 25, theOFS 130 determines the transported liquid type and communicates atransported liquid type to the system controller 70, as described above.Once the system controller 70 has determined the identity of the liquidproduct being loaded, the system controller 70 may either send a signalto the PGI controller 125 indicative of the transported liquid type asdetermined by the OFS 130 for indication on the PGI display 140 and/ormake the determination of the transported liquid type matches the loadedliquid type. In this embodiment, the loaded liquid type may either bederived from the loading arm tag 205 or from operator input into the PGIcontroller 125. For example, when the liquid product is a liquidpetroleum product, the PGI display 140 may display either “DistillateDetected” or “Gasoline Detected.”.

Where gasoline is detected, the PGI controller 125 may prompt the userto “Set Grade”, as noted above. In this embodiment, the operator mayselect from a variety of pre-programmed options to set the grade of theliquid product being loaded. The PGI controller 125 then communicates agrade signal encoding a grade selection to the system controller 70. Thesystem controller 70 compares the grade selection to the loading arm tag205 loaded liquid type and to the transported liquid type received fromthe OFS 130 to confirm a match. The system controller 70 stores, in acomputer readable medium, the transported liquid type for the tankcompartment 25 holding the liquid product based on either the loadedliquid type or the transported liquid type determined by the OFS 130.The process is repeated as other tank compartments 25 are filled in theproduct transport vehicle 15 with either the same liquid product or adifferent liquid product.

If the liquid product information from the tags does not match thetransported liquid type determined by the OFS 130 or does not match theloaded liquid type from the operator's input, the system controller 70may disable the transition of the valve from the normally locked stateto the unlocked state to prevent the flow of liquid product into thetank compartment 25. The PGI controller 125 may also indicate an erroron the PGI display 140 when a match is not made to warn the operator orthe system controller 70 may indicate the error on the display 80. Theindication may be an audible signal, visual display, etc. as describedbelow. In embodiments, the operator may override the system controller70 to enable the transition of the valve from the normally locked stateto the unlocked state and continue filling the tank compartment 25.

FIG. 13 schematically depicts the product transport vehicle 15 at adistribution facility unloading liquid product into a first distributiontank 65 a and a second distribution tank 65 b from a first tankcompartment 25 a and a second tank compartment 25 b, respectively. Theoperator initially chooses which tank compartment (e.g. the first tankcompartment 25 a or the second tank compartment 25 b) from which thefirst distribution tank 65 a and the second distribution tank 65 b willbe filled. If the first tank compartment 25 a is chosen to fill thefirst distribution tank 65 a, the operator may fluidly couple a firstdelivery hose 55 a to a first hose adaptor 133 a corresponding to thefirst tank compartment 25 a. The operator then fluidly couples a firsttank delivery connector 60 a to the first delivery hose 55 a and fluidlycouples the first tank delivery connector 60 a to the first distributiontank 65 a. The operator may repeat similar steps to fill the seconddistribution tank 65 b from the second tank compartment 25 b with eitherthe same liquid product type or a different liquid product type.

In some embodiments, the system controller 70 may confirm that eachdelivery hose 55 is properly connected to the distribution tank and atank compartment, as described hereinabove. In these embodiments, thesystem controller 70 prevents the discharge or unloading of product fromany tank compartment until at least one connection is confirmed. This isaccomplished by maintaining all the valves coupled to the tankcompartments in a normally locked state until the connections areconfirmed.

The first tank compartment 25 a is now fluidly connected to the firsthose adaptor 133 a, the first delivery hose 55 a, the first tankdelivery connector 60 a, and the first distribution tank 65 a.Similarly, the second tank compartment 25 b is now fluidly connected tothe second hose adaptor 133 b, the second delivery hose 55 b, the secondtank delivery connector 60 b, and the second distribution tank 65 b. Thesystem controller 70 then confirms that the fluid connections will notcross-contaminate the liquid products stored in the respectivedistribution tanks 65 a, 65 b.

In one embodiment, the process of product verification begins when thetank delivery connectors 60 a, 60 b are locked on to the correspondingdistribution tank 65 a, 65 b. For example, in one embodiment, the tankdelivery connectors 60 a, 60 b may include a locking lever and a locksensor, as described above, and power to the tank tag reader 95 is onlyprovided when the locking lever is in the locked position. Once thefirst locking lever 710 a is in the locked position, the first tank tagreader 95 a interrogates a first tank tag 110 a to retrieve the liquidproduct type, and other information encoded on the first tank tag 110 a.Alternatively, the operator may manually actuate a switch on the firsttank delivery connector 60 a to manually wake-up a first tank tag reader95 a. Once the first tank tag reader 95 a is powered on, the first tanktag reader 95 a interrogates the first tank tag 110 a and transmits astored liquid type signal indicative of the stored liquid type to thesystem controller 70. The first tank tag reader 95 a may use a firsttank connector antenna 115 a to transmit the stored liquid type signalto the system controller 70.

The system controller 70 may be configured to communicated with alimited number of tank tag readers. For example, the first tank tagreader 95 a and the second tank tag reader 95 b may be registered withthe system controller 70. The registration of one or more tank tagreaders to the system controller may eliminate any cross-talk with othertank tag readers from other product delivery trucks at the samedistribution station 20.

The system controller 70 receives the stored liquid product type signalfrom the first tank delivery connector 60 a and stores it in thecomputer-readable medium. The system controller 70 may then compare thestored liquid type to the transported liquid type contained in any ofthe tank compartments of the product transport vehicle to determine if amatch is present. If the system controller 70 determines that any tankcompartment contains a transported liquid type matching that of thestored liquid type, the system controller 70 transitions thecorresponding valve of that tank compartment from the normally lockedstate to the unlocked state, thereby allowing liquid product to bereleased from the corresponding tank compartment. However, if the systemcontroller 70 determines that a tank compartment does not contain atransported liquid type matching that of the stored liquid type, thesystem controller 70 maintains the corresponding valve of that tankcompartment in the normally locked state, thereby preventing the releaseof liquid product from the tank compartment.

Once the system controller 70 has determined that at least one tankcompartment contains a transported liquid type that matches the storedliquid type and transitioned the corresponding valve to an unlockedstate, the operator may operate the air selector valve for that tankcompartment (in this example, the first tank compartment 25 a) from anair selector valve panel (not shown) to manually (e.g. physically) openthe valve and allow the flow of the liquid product from the first tankcompartment 25 a.

In some embodiments, the system controller 70 may require the first PGIcontroller 125 a and/or the system controller 70 to receive a valve openair signal from an air selector valve panel (not shown) indicating theoperator has opened the valve to release the product from the first tankcompartment 25 a. In this embodiment, the system controller 70 mayprevent any other valves corresponding to any other tank compartmentsfrom being opened until the valve from the first tank compartment 25 ahas been physically closed after being opened (although it should beunderstood that the valve may remain in either the unlocked state or betransitioned to the normally unlocked state). Once the valvecorresponding to the first tank compartment 25 a has been physicallyclosed, the system controller 70 may allow the operator to repeatsimilar steps to fill the second distribution tank 65 b from the secondtank compartment 25 b with either the same liquid product type or adifferent liquid product type.

In some embodiments, if the system controller 70 detects a liquidproduct mismatch during one or more of the above connection sequences,it may provide the operator with a visual and/or audible warning. Forexample, in some embodiments the system controller 70 may instruct thefirst PGI controller 125 a or the second PGI controller 125 b to displaya warning to the operator. In some embodiments, the first PGI controller125 a and/or the second PGI controller 125 b may provide an audiblealert produced by an alerting device, a flashing message or color fromthe PGI display, and/or a visual device, such as one or more LEDs, tonotify the operator of the liquid product mismatch. In anotherembodiment, the system controller 70 may alert the operator if amismatch is determined. The system controller 70 may alert the operatorvia the display 80, an audible alert produced by an alerting device, aflashing message or color from the display 80, and/or a visual device,such as one or more LEDs, to notify the operator of the liquid productmismatch.

Referring to FIGS. 9, 10, and 13, in one embodiment, the OFS 130 may bepositioned in the pipe connection 50, as described above. When, the pipeconnection 50 is dry, such as when there is no liquid in either the pipeconnection 50 or the corresponding tank compartment 25 after the tankcompartment 25 was initially loaded through the manlid 30, the OFS 130may determine that a fluid is not present in the chamber 306 (FIG. 2) ofthe sensor housing 304 (FIG. 2), which may indicate that the pipeconnection 50 is dry (i.e., no liquid product is present in the tankcompartment 25 or the pipe connection 50). As previously described, theOFS 130 may generate the “no liquid present” message and may transmit,or alternately the system controller 70 may read, the “no liquidpresent” message, which may be indicative of an empty pipe condition.Upon receipt of this message, the PGI controller 125 and/or the systemcontroller 70 indicates on the PGI display 140, or alternately thedisplay 80, that the OFS 130 is not able to detect the presence of aliquid product in the tank compartment 25. For example, the fluidproduct type matching process may be initiated by waking-up the firsttank tag reader 95 a, as described above. The first tank tag reader 95 ainterrogates the first tank tag 110 a to retrieve the stored liquid typeindicative of the liquid product in the first distribution tank 65 a andtransmits the stored liquid type signal encoding the stored liquid typeto the system controller 70. The system controller 70 then transitionsthe valves corresponding to each tank compartment to the unlocked statefrom the normally locked state. This condition allows the operatorsystem controller to flood the pipe connection 50 with liquid productfrom the first tank compartment 25 a by opening the emergency valve 40.The OFS 130 associated with the now flooded pipe connection 50corresponding to the first tank compartment 25 a determines thetransported liquid type of the liquid product in each of the tankcompartments and sends the transported liquid type for each of thecompartments to the system controller 70. The system controller 70compares the transported liquid type received from the OFS 130 to thestored liquid type in each of the distribution tanks 65 a, 65 b. Foreach tank compartment which contains a transported liquid type whichmatches the stored liquid type, the system controller transitions thecontrol valve 45 corresponding to each tank compartment with thematching transported liquid type from a normally locked state to anunlocked state to allow the unloading of the liquid product from thecompartment by the operator. For those tank compartments in which thetransported liquid type and the stored liquid type do not match, thesystem controller 70 will maintain the corresponding control valve inthe normally locked state to ensure that the liquid product from tankcompartment is not unloaded and may also alert the operator to themismatch.

In embodiments where the OFS 130 is positioned in the tank compartment,this procedure to flood the pipe connection 50 may not be needed.

As indicated above, in some embodiments the system controller 70transitions the valves corresponding to each tank compartment from thenormally locked state to the unlocked state by the operator when thetank compartment is determined to contain a transported liquid typewhich matches the stored liquid type in a distribution tank. Thetransition from the normally locked state to the unlocked state allowsthe operator to then control the unloading of the liquid productmanually by opening or closing an air selector valve on an air selectorvalve panel. The air selector valve panel may be utilized to physicallyopen or close a valve corresponding to a tank compartment which containsa transported liquid type product matching the stored liquid type of adistribution tank. In other words, liquid product from a particular tankcompartment may not be unloaded from the tank compartment 25 if thesystem controller 70 has not transitioned a corresponding valve from anormally locked state to an unlocked state and the operator physicallyopens the valve utilizing the air selector.

Referring to FIGS. 9, 10, and 11A, if the OFS 130 transmits the “nofluid present” message to indicate that there is no fluid detected inthe chamber 306 (FIG. 2) of the sensor housing 304 (FIG. 2) (i.e., thereis no liquid product in the tank compartment 25), the PGI controller 125will display an “empty” status. If the OFS 130 determines that a fluidis present in the chamber 306 of the sensor housing 304, which indicatesthat liquid product is in the tank compartment, the accelerometer 78indicates the product transport vehicle 15 is in motion, and/or theparking brake is released, the PGI controller 125 may display a warning.For example, in one embodiment, the PGI controller 125 may display“Prior Product Grade” and “Retained Product” and “Frustrated Load” inalternating messages and prevent the valve of the plurality of valvescorresponding to the tank compartment 25 from being opened and theproduct unloading and/or loading process from proceeding when theproduct transport vehicle is in motion and/or the parking brake isreleased.

The system controller 70 may display an “unloading” status in thedisplay 80 as the liquid product is being unloaded from the tankcompartment 25 into the distribution tank 65. The OFS 130 may monitorwhether a fluid is present in the chamber 306 (FIG. 2) of the sensorhousing 304 (FIG. 2) and may transmit to the system controller 70 a“fluid present” message to indicate a wet status or a “no fluid present”message to indicate a dry status. The system controller 70 may use thewet status and the dry status to update the computer-readable mediumwith information on whether any liquid product remains in the tankcompartment 25 after unloading is complete.

Referring now to FIG. 17, a fleet management system 600 is shown. Thefleet management system 600 manages individual product transportvehicles 15 of a plurality of product transport vehicles as they travelabout a geographic region. The size of the geographic region may dependon the ability of the individual product transport vehicles 15 tocommunicate with a base station 605. For example, a radio communicationsystem may only provide a geographic region of about 50 miles, whereas acellular communication system may have a geographic region that isnationwide. Further, a satellite communication system may allow for ageographic region that is worldwide.

Referring not to FIGS. 9 and 17, to communicate with the base station605, the individual product transport vehicles 15 of the plurality ofproduct transport vehicles may include a global position system (GPS)antenna 610 and a transmitter antenna 615 communicatively coupled to thesystem controller 70. The system controller 70 receives from the GPSantenna a location signal indicative of a current location of theindividual product transport vehicles 15 of the plurality of producttransport vehicles. The transmitter antenna 615 may be a radio antenna,a cellular antenna, a satellite antenna or any antenna that matches thecommunication protocol (radio, cellular, satellite, etc.) of thecommunication system between the individual product transport vehicles15 of the plurality of product transport vehicles and the base station605.

The system controller 70 may transmit, using the transmitter antenna615, an ID signal indicative of the current location and a producttransport vehicle ID to the base station 605 at regular intervals toallow a fleet system controller 620 to receive the ID signal and trackthe current location and product transport vehicle ID of the individualproduct transport vehicles 15 of the plurality of product transportvehicles. In another embodiment, the system controller 70 may transmitthe ID signal only when the individual product transport vehicles 15 ofthe plurality of product transport vehicles is at a distribution station20 and/or unloading a tank compartment 25.

The base station 605 may include a receiver antenna 625 coupled to thebase station 605 and communicatively coupled to the transmitter antenna615 on the individual product transport vehicles 15 of the plurality ofproduct transport vehicles. The fleet system controller 620 may becommunicatively coupled to the receiver antenna 625 and a fleet display630. The fleet system controller 620 may include a processor and astorage medium containing computer readable and executable instructionswhich, when executed by the processor, cause the fleet system controller620 to automatically: receive the current location of the individualproduct transport vehicles 15 of the plurality of product transportvehicles; receive the vehicle identification; and record the currentlocation and the vehicle identification on the storage medium.

Still referring to FIGS. 9 and 17, the system controller 70 may have aLUT of stored locations of a plurality of distribution tank 65locations, the individual distribution tank locations indicated by GPScoordinates. The LUT may also include the proper stored liquid type ofthe distribution tanks 65 at each stored location. In anotherembodiment, the system controller 70 may receive a stored locationsignal indicative of the stored location of the distribution tank 65.The stored location signal may originate with the base station 605 andbe in response to receiving the ID signal with the individual producttransport vehicles 15 current location. In both embodiments describedabove, the stored location may include the GPS coordinates of thedistribution tank 65, a location liquid type indicative of the liquidproduct within the distribution tank 65, and other identifiableinformation, such as for example, the mailing address of thedistribution station 20 in which the distribution tank 65 is located,contact information for the responsible party for the distribution tank65, emergency contact information, and the like. The informationindicated by the stored location may be displayed on the display 80 orthe PGI display 140 (FIG. 11A) for the operator's use.

The system controller 70 may compare the current location indicated bythe location signal from the GPS antenna 610 to the stored location GPScoordinates to determine which distribution tanks 65 are at the currentlocation. From that determination, the system controller 70 may comparethe location liquid type to either the stored liquid type transmitted bythe tank tag reader 95 or the transported liquid type indicated by theOFS 130. From either of those comparisons, if they match, the systemcontroller may either enable the transition of the valve of theplurality of valves corresponding to the tank compartment 25 to allowthe unloading of the liquid product from the tank compartment 25 by theoperator or transition the valve of the plurality of valvescorresponding to the tank compartment 25 to the unlocked state from thenormally locked state. If, either of those comparisons indicates amis-match, the system controller 70 may disable the valve of theplurality of valves corresponding to the tank compartment 25 fromtransitioning from the normally locked state to the unlocked state.

The outcome of the comparisons described above between the stored liquidtype (either from the tank tag or operator input), location liquid type,and the transported liquid type, may be transmitted to the base station605 to be recorded on the computer readable medium by the fleet systemcontroller 620. Specifically, the system controller 70 may transmit,using the transmitter antenna 615, a lock data signal indicative of lockdata. The lock data may include the comparison results, the currentstate of individual valves of the plurality of valves, whether liquidproduct is or was unloaded, the amount of liquid product in each tankcompartment 25, and whether the operator has override the systemcontroller 70.

The physical location of the system controller 70 as shown in the FIGS.9, 12, and 13 are for illustration purposes only, and the systemcontroller 70 may be mounted in any location on the product transportvehicle 15. Furthermore, the product transport vehicle 15 may have morethan one transportation tank and the product transport vehicle 15 may bea fuel truck, an aircraft, or a ship and/or boat.

The crossover protection system 10 provides an automatic check and/orintervention to prevent the mixing of dissimilar products at adistribution station 20. The crossover protection system 10 uses the OFS130 to positively identify the fluid type of the liquid product to makea determination if the products match before allowing the products tomix in the distribution tank 65. Accordingly, human interaction orintervention to identify the product is not required.

The present disclosure may be embodied in hardware and/or in software(including firmware, resident software, micro-code, etc.). The systemcontroller 70 may have at least one processor and the computer-readablemedium. A computer-usable or the computer-readable medium or memorymodule may be any medium that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device.

The computer-usable or computer-readable medium or memory module may be,for example but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, device,or propagation medium. More specific examples (a non-exhaustive list) ofthe computer-readable medium would include the following: an electricalconnection having one or more wires, a portable computer diskette, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,and a portable compact disc read-only memory (CD-ROM). Note that thecomputer-usable or computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory.

Computer program code for carrying out operations of the presentdisclosure may be written in a high-level programming language, such asC or C++, for development convenience. In addition, computer programcode for carrying out operations of the present disclosure may also bewritten in other programming languages, such as, but not limited to,interpreted languages. Some modules or routines may be written inassembly language or even micro-code to enhance performance and/ormemory usage. However, software embodiments of the present disclosure donot depend on implementation with a particular programming language. Itwill be further appreciated that the functionality of any or all of theprogram modules may also be implemented using discrete hardwarecomponents, one or more application specific integrated circuits(ASICs), or a programmed digital signal processor or microcontroller.

While particular embodiments have been illustrated and described herein,it should be understood that various other changes and modifications maybe made without departing from the spirit and scope of the claimedsubject matter. Moreover, although various aspects of the claimedsubject matter have been described herein, such aspects need not beutilized in combination. It is therefore intended that the appendedclaims cover all such changes and modifications that are within thescope of the claimed subject matter.

What is claimed is:
 1. An optical fluid sensor comprising: a bodydefining a chamber and having one or more apertures to allow a fluid toenter the chamber; a light source optically coupled to the chamber andconfigured to emit light into the chamber; and a detector opticallycoupled to the chamber and configured to receive light from the chamber,wherein the detector measures an intensity of one or more wavelengths oflight received by the detector; the light source and the detector arepositioned such that, when fluid is disposed within the chamber, emittedlight from the light source passes into and through the fluid disposedin the chamber before being received by the detector.
 2. The opticalfluid sensor of claim 1, wherein the detector and the light source arepositioned facing one another; wherein the emitted light from the lightsource travels along a generally linear path from the light source,through the fluid in the chamber, and to the detector.
 3. The opticalfluid sensor of claim 1, further comprising a reflector.
 4. The opticalfluid sensor of claim 3, wherein the light source and the detector arepositioned at a first side of the chamber and the reflector ispositioned at a second side of the chamber, wherein when fluid isdisposed within the chamber, the emitted light from the light sourcetravels through the fluid in the chamber, reflects off of the reflector,and travels to the detector.
 5. The optical fluid sensor of claim 1,wherein the light source and the detector are fluidly isolated from thefluid by a transparent member positioned between the light source andthe chamber; wherein the transparent member allows light from the lightsource to pass through into the fluid.
 6. The optical fluid sensor ofclaim 1, further comprising at least one temperature sensor to measure atemperature of the light source or a fluid temperature.
 7. The opticalfluid sensor of claim 1, further comprising: a processor; one or morememory modules communicatively coupled to the processor; and machinereadable instructions stored in the one or more memory modules thatcause the optical fluid sensor to perform at least the following whenexecuted by the processor: transmit a control signal to the light sourceto cause the light source to emit IR light into the chamber; receive IRlight at the detector; process the IR light received at the detector todetermine an intensity of the received IR light; compare the intensityof the received IR light to a threshold intensity; and determine that afluid is present if the intensity of the received IR light is less thanthe threshold intensity of IR light.
 8. The optical fluid sensor ofclaim 1, further comprising: a processor; one or more memory modulescommunicatively coupled to the processor; and machine readableinstructions stored in the one or more memory modules that cause theoptical fluid sensor to perform at least the following when executed bythe processor: transmit a control signal to the light source to causethe light source to emit visible light into the chamber; receive visiblelight at the detector; process the received light to determinewavelength and intensity information for the received light; compare thewavelength and intensity information for the received light to one ormore fluid profiles stored in the one or more memory modules; anddetermine a fluid type of the fluid in the chamber based on thecomparison.
 9. The optical fluid sensor of claim 8, further comprisingmachine readable instructions stored in the one or more memory modulesthat cause the sensor to perform at least the following when executed bythe processor: transmit a control signal to the light source to causethe light source to emit UV light into the chamber in order to cause thefluid to fluoresce visible light; receive visible light at the detector;process the received light to determine wavelength and intensityinformation for the received light; compare the wavelength and intensityinformation for the received light to the one or more fluid profilesstored in the one or more memory modules, wherein each of the one ormore fluid profiles comprises information on one or more fluorescentproperties of the fluid; and determine a fluid type of the fluid in thechamber based on the comparison.
 10. The optical fluid sensor of claim9, further comprising machine readable instructions stored in the one ormore memory modules that cause the optical fluid sensor to perform atleast the following when executed by the processor: receive atemperature signal from a temperature sensor; and adjust the fluidprofiles stored in the one or more memory modules or the wavelength andintensity information of the received light based on the temperaturesignal.
 11. A crossover protection system comprising: a producttransport vehicle comprising a tank compartment for containing a liquidproduct; a valve coupled to the tank compartment, the valve regulating aflow of liquid product from the tank compartment and having a normallylocked state; the optical fluid sensor of claim 1 positioned to contactthe liquid product stored in the tank compartment; a tank deliveryconnector fluidly coupled to a distribution side of the valve, the tankdelivery connector comprising a tank tag reader for interrogating a tanktag coupled to a distribution tank separate from the product transportvehicle to retrieve a stored liquid type encoded on the tank tag,wherein the stored liquid type is indicative of a type of the liquidproduct in the distribution tank; and a system controllercommunicatively coupled to the valve, the optical fluid sensor, and thetank delivery connector, the system controller comprising a processorand one or more memory modules communicatively coupled to the processor.12. The crossover protection system of claim 11, further comprisingmachine readable instructions stored in the one or more memory modulesthat cause the sensor to perform at least the following when executed bythe processor: determine a transported liquid type based on an outputfrom the optical fluid sensor; receive the stored liquid type signaltransmitted by the tank delivery connector; determine the stored liquidtype based on the stored liquid type signal; compare the transportedliquid type to the stored liquid type; maintain the valve in thenormally locked state when the stored liquid type and the transportedliquid type do not match to prevent the flow of liquid product from thetank compartment; and transition the valve from the normally lockedstate to an unlocked state when the stored liquid type and thetransported liquid type match, thereby permitting the flow of liquidproduct from the tank compartment.
 13. A fuel sensor comprising: a lightsource optically coupleable to an enclosed volume and configured to emitIR, visible, and UV spectra light; a detector optically coupleable tothe enclosed volume and configured to output a signal proportional to anintensity of one or more wavelengths of IR or visible light received bythe detector; a processor; one or more memory modules communicativelycoupled to the processor; and machine readable instructions stored inthe one or more memory modules that cause the fuel sensor to perform atleast the following when executed by the processor: send a controlsignal to the light source to cause the light source to emit visiblelight into the enclosed space and emit UV light into the enclosed space;receive visible light at the detector; process the received light todetermine wavelength and intensity information for the received light;and determine a fluid type of the fluid in the chamber from thewavelength and intensity information for the received light.
 14. Theoptical fuel sensor of claim 13, further comprising a reflector, whereinthe light source and the detector are positioned at one side of thechamber and the reflector is positioned at another side of the chamberto reflect emitted light from the light source towards the detector. 15.The optical sensor of claim 13, wherein emitted light from the lightsource or fluoresced light fluoresced by the fluid travels through thefluid disposed within the chamber before being received by the detector.16. The optical sensor of claim 13, further comprising: a processor; oneor more memory modules communicatively coupled to the processor; andmachine readable instructions stored in the one or more memory modulesthat cause the fuel sensor to perform at least the following whenexecuted by the processor: send a control signal to the light source tocause the light source to emit UV light into the chamber in order tocause the fluid to fluoresce visible light; receive visible light at thedetector; process the received light to determine wavelength andintensity information for the received light; compare the wavelength andintensity information for the received light to the one or more fluidprofiles stored in the one or more memory modules; and determine a fluidtype of the fluid in the chamber based on the comparison, wherein eachof the one or more fluid profiles comprises information on one or morefluorescent properties of the fluid.
 17. An optical sensor systemcomprising: a light source configured to emit UV light into a fluid; adetector configured to measure intensities of one or more wavelengths ofvisible light fluoresced by the fluid in response to the UV lightemitted by the light source; a processor; one or more memory modulescommunicatively coupled to the processor; and machine readableinstructions stored in the one or more memory modules that cause theoptical sensor system to perform at least the following when executed bythe processor: transmit a control signal to the light source to causethe light source to emit the UV light into the fluid to cause the fluidto fluoresce; receive visible light at the detector; process thereceived light to determine wavelength and intensity information for thereceived light; compare the wavelength and intensity information for thereceived light to one or more fluid profiles stored in the one or morememory modules, wherein each of the one or more fluid profiles comprisesinformation on one or more fluorescent properties of the fluid; anddetermine a fluid type of the fluid based on the comparison.
 18. Acrossover protection system comprising: a product transport vehiclecomprising a tank compartment for containing a liquid product; a valvecoupled to the tank compartment, the valve regulating a flow of liquidproduct from the tank compartment and having a normally locked state; anoptical fluid sensor positioned to contact the liquid product stored inthe tank compartment, the optical fluid sensor comprising: a bodydefining a chamber and having one or more apertures to allow the liquidproduct to enter the chamber; a light source optically coupled to thechamber and configured to emit light into the chamber; a detectoroptically coupled to the chamber and configured to receive light fromthe chamber; wherein the detector measures an intensity of one or morewavelengths of light received by the detector, and the light source andthe detector are positioned such that, when fluid is disposed within thechamber, light passes into and through the fluid disposed within thechamber before being received by the detector; a tank delivery connectorfluidly coupled to a distribution side of the valve, the tank deliveryconnector comprising a tank tag reader for interrogating a tank tagcoupled to a distribution tank separate from the product transportvehicle to retrieve a stored liquid type encoded on the tank tag,wherein the stored liquid type is indicative of a type of the liquidproduct in the distribution tank; and a system controllercommunicatively coupled to the valve, the optical fluid sensor, and thetank delivery connector, the system controller comprising a processorand one or more memory modules.
 19. The crossover protection system ofclaim 18, further comprising machine readable instructions stored in theone or more memory modules that cause the crossover protection system toperform at least the following when executed by the processor: determinea transported liquid type based on an output from the optical fluidsensor; receive the stored liquid type signal transmitted by the tankdelivery connector; determine the stored liquid type based on the storedliquid type signal; compare the transported liquid type to the storedliquid type; maintain the valve in the normally locked state when thestored liquid type and the transported liquid type do not match toprevent the flow of liquid product from the tank compartment; andtransition the valve from the normally locked state to an unlocked statewhen the stored liquid type and the transported liquid type match,thereby permitting the flow of liquid product from the tank compartment.20. The crossover protection system of claim 18, wherein the valve is acontrol valve.
 21. The crossover protection system of claim 18, furthercomprising a lock mechanism coupled to the tank delivery connector, thelock mechanism comprising a locking lever with a locked position and anunlocked position, the lock mechanism mechanically securing the tankdelivery connector to the distribution tank when the locking lever is inthe locked position.
 22. The crossover protection system of claim 21,further comprising a lock sensor for sensing whether the locking leveris in the locked position or the unlocked position.
 23. The crossoverprotection system of claim 18, wherein power to the tank tag reader isonly provided when the locking lever is in the locked position.
 24. Thecrossover protection system of claim 18, wherein the detector and thelight source of the optical fluid sensor are positioned facing oneanother; wherein emitted light from the light source travels along agenerally linear path from the light source, through the liquid productin the chamber, and to the detector.
 25. The crossover protection systemof claim 18, wherein the optical fluid sensor further comprises areflector.
 26. The crossover protection system of claim 25, wherein thelight source and the detector of the optical fluid sensor are positionedat a first side of the chamber and the reflector is positioned at asecond side of the chamber, wherein when the liquid product is disposedwithin the chamber, emitted light from the light source travels throughthe liquid product in the chamber, reflects off of the reflector, andtravels to the detector.